[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 Jul 2017 08:35:21 -0400
From: Theodore Ts'o <tytso@....edu>
To: Ulrich Windl <Ulrich.Windl@...uni-regensburg.de>
Cc: "Nicholas A.Bellinger" <nab@...ux-iscsi.org>,
David Miller <davem@...emloft.net>,
Eric Biggers <ebiggers3@...il.com>,
open-iscsi <open-iscsi@...glegroups.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Chris Leech <cleech@...hat.com>, Lee Duncan <lduncan@...e.com>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
linux-kernel@...r.kernel.org,
target-devel <target-devel@...r.kernel.org>,
"Jason A.Donenfeld" <Jason@...c4.com>
Subject: Re: Antw: Re: Re: [PATCH v4 06/13] iscsi: ensure
RNG is seeded before use
On Wed, Jul 05, 2017 at 09:03:43AM +0200, Ulrich Windl wrote:
> > Note, during the development of my /dev/random implementation, I added the
> > getrandom-like blocking behavior to /dev/urandom (which is the equivalent to
> > Jason's patch except that it applies to user space). The boot process locked
>
> I thought reads from urandom never block by definition. An older manual page
> (man urandom) also says: "A read from the /dev/urandom device will not
> block waiting for more entropy."
As I said in my original message, I *tried* this as an experiment.
Because lots of security-obsessed people were disputing my
intelligence, my judgement, and in some cases, my paternity becuase I
wouldn't change /dev/urandom not to block.
So I did the experiment so I could give them hard data about why we
couldn't go down that path.
> > up since systemd wanted data from /dev/urandom while it processed the
> > initramfs. As it did not get any, the boot process did not commence that
> > could
> > deliver new events to be picked up by the RNG.
And indeed, making this change brick'ed at least one version of Ubuntu
and one version of CeroWRT, as reported by the kernel's 0-day testing
system. As a result, this patch (which was always a proof of concept,
not anything I thought had any chance of going upstream), was dropped.
Since in the kernel, We Do Not Break Backwards Compatibility, this is
why we have a new interface --- getrandom(2) --- instead of changing
an existing interface. (Well, there were multiple good reasons for
getrandom, but this was definitely one of them.)
- Ted
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
