[Cryptography] Random numbers only once

Kevin W. Wall kevin.w.wall at gmail.com
Tue Feb 4 20:29:50 EST 2014


On Tue, Feb 4, 2014 at 8:16 PM, Richard Outerbridge <outer at interlog.com> wrote:
>
> On 2014-02-04 (35), at 19:59:37, Watson Ladd <watsonbladd at gmail.com> wrote:
>
> > On Tue, Feb 4, 2014 at 4:55 PM, Kevin W. Wall <kevin.w.wall at gmail.com> wrote:
> >> On Tue, Feb 4, 2014 at 2:19 AM, Tony Arcieri <bascule at gmail.com> wrote:
> >>> On Mon, Feb 3, 2014 at 9:12 PM, Watson Ladd <watsonbladd at gmail.com> wrote:
>
> [....]
>
> >> As for whether or not /dev/random should block, that has already been
> >> discussed at length here and elsewhere. However, I think most of us
> >> would concede that blocking is better than returning predictable
> >> pseudo-random values to the caller.
> >
> > But that only justifies blocking exactly once after boot.
>
> What he said.
> __outer

AND??? I wasn't making a comment on whether or not blocking was
a good idea or not. Like I said, that would just be rehashing old posts.
This was only an observation that the implementors could have done
things a lot worse.

-kevin
-- 
Blog: http://off-the-wall-security.blogspot.com/
NSA: All your crypto bit are belong to us.


More information about the cryptography mailing list