From: Dominik Brodowski <linux@dominikbrodowski.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Thomas Ristenpart <ristenpart@cornell.edu>,
Yevgeniy Dodis <dodis@cs.nyu.edu>, tytso <tytso@mit.edu>,
Nadia Heninger <nadiah@cs.ucsd.edu>,
Noah Stephens-Dawidowitz <noahsd@gmail.com>,
Stefano Tessaro <tessaro@cs.washington.edu>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"D. J. Bernstein" <djb@cr.yp.to>,
"jeanphilippe.aumasson@gmail.com"
<jeanphilippe.aumasson@gmail.com>,
"jann@thejh.net" <jann@thejh.net>,
"keescook@chromium.org" <keescook@chromium.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Peter Schwabe <peter@cryptojedi.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: is "premature next" a real world rng concern, or just an academic exercise?
Date: Fri, 13 May 2022 08:19:13 +0200 [thread overview]
Message-ID: <Yn34YWhH1nSa8O8K@owl.dominikbrodowski.net> (raw)
In-Reply-To: <YnzzuuLPssc3/tVe@zx2c4.com>
Am Thu, May 12, 2022 at 01:47:06PM +0200 schrieb Jason A. Donenfeld:
> But on the other hand, it appears that none of us really thinks that
> premature next is a real problem worth complicating designs over. So
> maybe we can just say that it is nice when the silicon in one way or
> another helps with premature next, but maybe not an explicit must have.
> So where does that leave us?
>
> - Systems with RDSEED/RDRAND don't have premature next, due to the above
> KDF salt. This is probably the majority of systems out there these
> days. This also applies to the sleep resumption notification (and the
> vmgenid one), and I suspect that most systems with S3 or S0ix or
> whatever else these days also probably have RDRAND.
... and most of these systems have TPM chips with a RNG, which is (alas)
usually only used at system startup, as that hw_rng device sets its quality
to 0 (meaning untrusted). So there's also room for improvement involving
these hw rng devices.
Thanks,
Dominik
next prev parent reply other threads:[~2022-05-13 6:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:58 is "premature next" a real world rng concern, or just an academic exercise? Jason A. Donenfeld
2022-04-28 4:26 ` Nadia Heninger
2022-04-30 2:08 ` Sandy Harris
2022-05-01 0:49 ` tytso
2022-05-01 11:16 ` Jason A. Donenfeld
[not found] ` <CAMvzKsiA52Si=PzOJXYwGSA1WUz-1S0A8cpgRJWDzpMkfFbX+Q@mail.gmail.com>
2022-05-09 15:55 ` Yevgeniy Dodis
2022-05-10 15:21 ` Jason A. Donenfeld
2022-05-10 18:51 ` D. J. Bernstein
2022-05-10 20:09 ` Jason A. Donenfeld
2022-05-10 21:33 ` Simo Sorce
2022-05-10 22:50 ` Jason A. Donenfeld
2022-05-11 20:26 ` Thomas Ristenpart
2022-05-12 11:47 ` Jason A. Donenfeld
2022-05-13 6:19 ` Dominik Brodowski [this message]
2022-05-11 20:46 ` Pavel Machek
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=Yn34YWhH1nSa8O8K@owl.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=Jason@zx2c4.com \
--cc=djb@cr.yp.to \
--cc=dodis@cs.nyu.edu \
--cc=gregkh@linuxfoundation.org \
--cc=jann@thejh.net \
--cc=jeanphilippe.aumasson@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nadiah@cs.ucsd.edu \
--cc=noahsd@gmail.com \
--cc=peter@cryptojedi.org \
--cc=ristenpart@cornell.edu \
--cc=tessaro@cs.washington.edu \
--cc=torvalds@linux-foundation.org \
--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).