From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: smueller@chronox.de
Cc: dhowells@redhat.com, james.l.morris@oracle.com, serge@hallyn.com,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kirill Marinushkin <k.marinushkin@gmail.com>
Subject: Re: [PATCH] KEYS: fix big_key dependency
Date: Tue, 16 Aug 2016 22:02:12 +0200 [thread overview]
Message-ID: <1471377732-32290-1-git-send-email-k.marinushkin@gmail.com> (raw)
In-Reply-To: <2554221.UGXOTzxq81@tauon.atsec.com>
> May I suggest CRYPTO_DRBG?
Hello Ciao,
Thanks for your proposal. I submitted the PATCH v2 where I use
CRYPTO_RNG_DEFAULT the same way it is used in crypto/Kconfig.
It solves the issue, too. In addition, it selects CRYPTO_DRBG_MENU,
which is a more universal use-case, as I understood from your comment.
Best Regards,
Kirill
prev parent reply other threads:[~2016-08-16 20:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 22:45 Kirill Marinushkin
2016-08-16 5:48 ` Stephan Mueller
2016-08-16 19:51 ` [PATCH v2] " Kirill Marinushkin
2016-08-16 20:02 ` Kirill Marinushkin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1471377732-32290-1-git-send-email-k.marinushkin@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=smueller@chronox.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®