From: Stephan Mueller <smueller@chronox.de>
To: Kirill Marinushkin <k.marinushkin@gmail.com>
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
Subject: Re: [PATCH] KEYS: fix big_key dependency
Date: Tue, 16 Aug 2016 07:48:47 +0200 [thread overview]
Message-ID: <2554221.UGXOTzxq81@tauon.atsec.com> (raw)
In-Reply-To: <1471301139-28702-1-git-send-email-k.marinushkin@gmail.com>
Am Dienstag, 16. August 2016, 00:45:39 CEST schrieb Kirill Marinushkin:
Hi Kirill,
> + select CRYPTO_ANSI_CPRNG
This change enables the RNG which will not pass FIPS testing any more. Hence,
this selection could cause an issue in FIPS mode (i.e. booting the kernel with
fips=1).
May I suggest CRYPTO_DRBG?
Ciao
Stephan
next prev parent reply other threads:[~2016-08-16 5:48 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 [this message]
2016-08-16 19:51 ` [PATCH v2] " Kirill Marinushkin
2016-08-16 20:02 ` [PATCH] " Kirill Marinushkin
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=2554221.UGXOTzxq81@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=k.marinushkin@gmail.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
/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®