mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stephan Müller" <smueller@chronox.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-hardening@lists.openwall.com
Subject: Re: get_random_bytes returns bad randomness before seeding is complete
Date: Sun, 04 Jun 2017 07:48:26 +0200	[thread overview]
Message-ID: <2400574.rYAxqaUNNq@positron.chronox.de> (raw)
In-Reply-To: <CAHmME9q=AdK7BHQw0+sd4T0HGQce92KXTD+-TTc2s2CXbEHAAA@mail.gmail.com>

Am Freitag, 2. Juni 2017, 16:59:56 CEST schrieb Jason A. Donenfeld:

Hi Jason,

> 
> Alternatively, I'm open to other solutions people might come up with.

How about stirring in some data from the Jitter RNG that we have in the kernel 
already and that is used for the DRBG in case get_random_bytes has 
insufficient entropy? Yes, two kernel developers said that this RNG is 
useless, where in fact a lot of hardware and even crypto folks say that this 
approach has merits.

In any case, it cannot destroy the (not present) entropy at boot time anyway. 
Thus, take some 32, 48 or 64 bytes from it right at the start of the kernel, 
and we should be better (from the view point of quite some folks) or not worse 
off (view point of two developers here).

As this RNG does not depend on any in-kernel facility, it is always available 
at any time.

PS: I could revive a patch adding this to random.c that I sent long ago if 
desired.

Ciao
Stephan

  parent reply	other threads:[~2017-06-04  5:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 14:59 Jason A. Donenfeld
2017-06-02 15:53 ` Jason A. Donenfeld
2017-06-02 16:48   ` Jason A. Donenfeld
2017-06-02 17:41   ` [kernel-hardening] " Daniel Micay
2017-06-02 17:46     ` Jason A. Donenfeld
2017-06-02 18:58     ` Kees Cook
2017-06-02 17:26 ` Theodore Ts'o
2017-06-02 17:44   ` Jason A. Donenfeld
2017-06-02 19:07     ` Theodore Ts'o
2017-06-02 23:58       ` Jason A. Donenfeld
2017-06-03  0:20         ` [kernel-hardening] " Sandy Harris
2017-06-03  2:32         ` [PATCH RFC 0/3] get_random_bytes seed blocking Jason A. Donenfeld
2017-06-03  2:32           ` [PATCH RFC 1/3] random: add synchronous API for the urandom pool Jason A. Donenfeld
2017-06-03  2:32           ` [PATCH RFC 2/3] random: add get_random_{bytes,u32,u64,int,long}_wait family Jason A. Donenfeld
2017-06-03  2:32           ` [PATCH RFC 3/3] random: warn when kernel uses unseeded randomness Jason A. Donenfeld
2017-06-03  5:04         ` get_random_bytes returns bad randomness before seeding is complete Theodore Ts'o
2017-06-03 12:30           ` Jason A. Donenfeld
2017-06-03 21:45             ` Sandy Harris
2017-06-03 22:54               ` Jeffrey Walton
2017-06-03 23:55                 ` [kernel-hardening] " Daniel Micay
2017-06-04  5:55                 ` Stephan Müller
2017-06-04  5:48 ` Stephan Müller [this message]
2017-06-04  5:54   ` Jeffrey Walton
2017-06-04  6:23 ` Stephan Müller

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=2400574.rYAxqaUNNq@positron.chronox.de \
    --to=smueller@chronox.de \
    --cc=Jason@zx2c4.com \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®