From: Randy Dunlap <rdunlap@infradead.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Theodore Ts'o <tytso@mit.edu>,
"H . Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] random: remove "nordrand" flag in favor of "random.trust_cpu"
Date: Wed, 6 Jul 2022 17:12:13 -0700 [thread overview]
Message-ID: <2603a1c4-ef5d-7719-b458-e70da180b878@infradead.org> (raw)
In-Reply-To: <20220707000021.504308-1-Jason@zx2c4.com>
Hi Jason,
On 7/6/22 17:00, Jason A. Donenfeld wrote:
> The decision of whether or not to trust RDRAND is controlled by the
> "random.trust_cpu" boot time parameter or the CONFIG_RANDOM_TRUST_CPU
> compile time default. The "nordrand" flag was added during the early
> days of RDRAND, when there were worries that merely using its values
> could compromise the RNG. However, these days, RDRAND values are not
> used directly but always go through the RNG's hash function, making
> "nordrand" no longer useful.
>
> Rather, the correct switch is "random.trust_cpu", which not only handles
> the relevant trust issue directly, but also is general to multiple CPU
> types, not just x86.
>
> However, x86 RDRAND does have a history of being occassionally
occasionally
> problematic. Prior, when the kernel would notice something strange, it'd
> warn in dmesg and suggest enabling "nordrand". We can improve on that by
> making the test a little bit better and then taking the step of
> automatically disabling "nordrand" if we detect it's problematic.
enabling
? I.e., disabling RDRAND and RDSEED.
>
> Also extend the basic sanity test to RDSEED in addition to RDRAND, and
> disable both if either one fails.
>
> Cc: x86@kernel.org
> Cc: Theodore Ts'o <tytso@mit.edu>
> Suggested-by: H. Peter Anvin <hpa@zytor.com>
> Suggested-by: Borislav Petkov <bp@suse.de>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> This patch builds on top of v4 of "random: remove CONFIG_ARCH_RANDOM":
> https://lore.kernel.org/lkml/20220706143521.459565-1-Jason@zx2c4.com/
>
> .../admin-guide/kernel-parameters.txt | 5 --
> arch/x86/kernel/cpu/amd.c | 2 +-
> arch/x86/kernel/cpu/rdrand.c | 73 +++++++++----------
> 3 files changed, 36 insertions(+), 44 deletions(-)
> diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> index 0c0b09796ced..216fc2f53cbe 100644
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> @@ -808,7 +808,7 @@ static void clear_rdrand_cpuid_bit(struct cpuinfo_x86 *c)
> return;
>
> /*
> - * The nordrand option can clear X86_FEATURE_RDRAND, so check for
> + * The self test can clear X86_FEATURE_RDRAND, so check for
Preferably: self-test
> * RDRAND support using the CPUID function directly.
> */
> if (!(cpuid_ecx(1) & BIT(30)) || rdrand_force)
--
~Randy
next prev parent reply other threads:[~2022-07-07 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 0:00 Jason A. Donenfeld
2022-07-07 0:12 ` Randy Dunlap [this message]
2022-07-07 0:14 ` Jason A. Donenfeld
2022-07-09 10:43 ` [PATCH random v2] x86/rdrand: Remove " Jason A. Donenfeld
2022-07-09 11:30 ` Borislav Petkov
2022-07-17 11:38 ` [PATCH v3] " Jason A. Donenfeld
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=2603a1c4-ef5d-7719-b458-e70da180b878@infradead.org \
--to=rdunlap@infradead.org \
--cc=Jason@zx2c4.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=x86@kernel.org \
/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®