From: "H. Peter Anvin" <hpa@zytor.com>
To: James Morris <jamorris@linux.microsoft.com>,
Stephan Mueller <smueller@chronox.de>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"David Miller" <davem@davemloft.net>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"John Haxby" <john.haxby@oracle.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Simo Sorce" <simo@redhat.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
"Mickaël Salaün" <mic@linux.microsoft.com>,
tytso@mit.edu
Subject: Re: [PATCH v1] crypto: Make the DRBG compliant with NIST SP800-90A rev1
Date: Wed, 23 Jun 2021 13:49:24 -0700 [thread overview]
Message-ID: <98006AFB-C40E-46F7-BE88-D8E66653B71B@zytor.com> (raw)
In-Reply-To: <a4e1c071-32af-9650-e6fd-8943b3a79bb0@linux.microsoft.com>
This one really does keep coming back like yesterday's herring, doesn't it...
On June 23, 2021 10:00:29 AM PDT, James Morris <jamorris@linux.microsoft.com> wrote:
>On Wed, 23 Jun 2021, Stephan Mueller wrote:
>
>>
>> > These changes replace the use of the Linux RNG with the Jitter RNG,
>> > which is NIST SP800-90B compliant, to get a proper entropy input
>and a
>> > nonce as defined by FIPS.
>>
>> Can you please help me understand what is missing in the current code
>which
>> seemingly already has achieved this goal?
>
>The advice we have is that if an attacker knows the internal state of
>the
>CPU, then the output of the Jitter RNG can be predicted.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
prev parent reply other threads:[~2021-06-23 20:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 12:07 [PATCH v1] crypto: Make the DRBG compliant with NIST SP800-90A rev1 Mickaël Salaün
2021-06-23 14:22 ` Stephan Mueller
2021-06-23 17:00 ` James Morris
2021-06-23 17:27 ` Stephan Müller
2021-06-23 18:04 ` Mickaël Salaün
2021-06-23 19:10 ` Stephan Mueller
2021-06-24 10:13 ` Mickaël Salaün
2021-06-24 11:50 ` Stephan Mueller
2021-06-25 11:09 ` Mickaël Salaün
2021-06-25 13:50 ` Stephan Müller
2021-06-25 14:53 ` Mickaël Salaün
2021-06-23 20:49 ` H. Peter Anvin [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=98006AFB-C40E-46F7-BE88-D8E66653B71B@zytor.com \
--to=hpa@zytor.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jamorris@linux.microsoft.com \
--cc=john.haxby@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mic@linux.microsoft.com \
--cc=simo@redhat.com \
--cc=smueller@chronox.de \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).