From: Jeff Dike <jdike@addtoit.com>
To: Rob Landley <rob@landley.net>
Cc: user-mode-linux-devel@lists.sourceforge.net, 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 13:45:46 -0500 [thread overview]
Message-ID: <200503111845.j2BIjkJp003341@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 10 Mar 2005 13:41:37 EST." <200503101341.37346.rob@landley.net>
rob@landley.net said:
> I'm just thinking about those UML hosting farms, with several UML
> instances per machine, on machines which haven't got a keyboard
> attached constantly feeding entropy into the pool. If just ONE of
> them is serving ssl connections from its own /dev/urandom, that would
> drain the /dev/random entropy pool on the host machine almost
> immediately...
All true (except for that last reference to urandom), but also irrelevant to
whether UML's hwrng should be hooked up to the host's /dev/random or not.
As far as I can see, the only thing that matters is that hwrng should produce
real randomness, and that can only be had by reading /dev/random (or maybe
the host's /dev/hwrng, but that's supposed to be fed into /dev/random anyway).
So, hooking up the UML /dev/hwrng to the host's /dev/urandom would be lying.
If the host's entropy pool gets drained as a result, I would say that's an
application bug, and not a reason for UML to get its randomness from the
host's /dev/urandom.
Jeff
next prev parent reply other threads:[~2005-03-11 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:15 Jeff Dike
2005-03-10 18:41 ` [uml-devel] " Rob Landley
2005-03-11 18:45 ` Jeff Dike [this message]
2005-03-11 19:04 ` Chris Friesen
2005-03-11 18:54 ` Blaisorblade
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=200503111845.j2BIjkJp003341@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®