From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] exportfs security question
Date: Fri, 10 Apr 2009 11:25:02 +0100 [thread overview]
Message-ID: <4ef85060c676ccc031ac92c171b73155@quintile.net> (raw)
In-Reply-To: <20090410084102.GG4823@masters6.cs.jhu.edu>
> truerand() returns (at most) 32 bits of entropy, which gets pushed into
> srand() and then 32 bits of entropy are read back out... why not just use
> truerand() directly?
This bit I know, truerand() reads /dev/random (see cons(1)) and
can only generate "a few hundred bits per second".
rand is pretty good (I think) but it is predictable, by seeding it from
truerand() the predictability is avoided.
-Steve.
next prev parent reply other threads:[~2009-04-10 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 8:41 Nathaniel W Filardo
2009-04-10 10:25 ` Steve Simon [this message]
2009-04-10 15:18 ` Nathaniel W Filardo
2009-04-10 11:48 ` erik quanstrom
2009-04-10 12:08 ` Mechiel Lukkien
2009-04-10 15:17 ` Nathaniel W Filardo
2009-04-11 23:24 ` Russ Cox
2009-04-13 4:45 ` lucio
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=4ef85060c676ccc031ac92c171b73155@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).