From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Rob Landley <rob@landley.net>, Jeff Dike <jdike@addtoit.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] [PATCH 3/9] UML - "Hardware" random number generator
Date: Fri, 11 Mar 2005 19:54:33 +0100 [thread overview]
Message-ID: <200503111954.33414.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200503101341.37346.rob@landley.net>
On Thursday 10 March 2005 19:41, Rob Landley wrote:
> On Wednesday 09 March 2005 09:15 pm, Jeff Dike wrote:
> > This implements a hardware random number generator for UML which attaches
> > itself to the host's /dev/random.
>
> Direct use of /dev/random always makes me nervous. I've had a recurring
> problem with /dev/random blocking,
The fd is set in non-blocking mode on opening, so when there is no data UML
will not block but get -EAGAIN (which is then handled by waiting and
retrying).
> and generally configure as much as
> possible to use /dev/urandom instead. It's really easy for a normal user
> to drain the /dev/random entropy pool on a server (at least one that
> doesn't have a sound card you can tell it to read white noise from).
> cat /dev/random > /dev/null
> I like /dev/urandom because it'll feed you as much entropy as it's got,
Yes, and entropy will gradually degrade...
> but
> won't block, and will presumably round-robin insert real entropy in the
> streams that multiple users get from /dev/urandom. (I realize this may not
> be the best place to get gpg keys from.)
> Admittedly if UML used /dev/urandom instead of /dev/random, it wouldn't
> know how much "real" randomness it was getting and how much synthetic
> randomness, but this makes predicting the numbers it's producing easier
> how?
Don't ask us..., we just recycle the others knowledge... however in short when
you say that "randomness" (or entropy) is not the maximum, you mean that
there is some redundancy, i.e. some law to ease predicting subsequent
numbers. For instance some character is more frequent than another... And
this is also the same kind of things that is exploited during compression...
the more compressed are your data, the less entropy they have before
compression (I'm not an expert of Shannon information entropy theories,
however, but this is what I grasped).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-03-11 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:15 [uml-devel] [PATCH 3/9] UML - "Hardware" random number generator Jeff Dike
2005-03-10 18:41 ` Rob Landley
2005-03-11 18:45 ` Jeff Dike
2005-03-11 19:04 ` Chris Friesen
2005-03-11 18:54 ` Blaisorblade [this message]
2005-03-11 20:23 ` Bill Davidsen
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=200503111954.33414.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.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