Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 16 Jun 2017 20:45:57 -0700
From: Lee Duncan <>
To: "Jason A. Donenfeld" <>
Cc: Theodore Ts'o <>,
 Linux Crypto Mailing List <>,
 LKML <>,,
 Greg Kroah-Hartman <>,
 David Miller <>, Eric Biggers <>,
 "Nicholas A. Bellinger" <>,
 Chris Leech <>,
Subject: Re: Re: [PATCH v4 06/13] iscsi: ensure RNG is
 seeded before use

On 06/16/2017 05:41 PM, Jason A. Donenfeld wrote:
> Hi Lee,
> On Fri, Jun 16, 2017 at 11:58 PM, Lee Duncan <> wrote:
>> It seems like what you are doing is basically "good", i.e. if there is
>> not enough random data, don't use it. But what happens in that case? The
>> authentication fails? How does the user know to wait and try again?
> The process just remains in interruptible (kill-able) sleep until
> there is enough entropy, so the process doesn't need to do anything.
> If the waiting is interrupted by a signal, it returns -ESYSRESTART,
> which follows the usual semantics of restartable syscalls.
> Jason

In your testing, how long might a process have to wait? Are we talking
seconds? Longer? What about timeouts?

Sorry, but your changing something that isn't exactly broken, so I just
want to be sure we're not introducing some regression, like clients
can't connect the first 5 minutes are a reboot.
Lee Duncan

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.