From: Jeff Dike <jdike@karaya.com>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, user-mode-linux-user@lists.sourceforge.net
Subject: Re: user-mode port 0.56-2.4.18-15
Date: Tue, 09 Apr 2002 20:44:24 -0500 [thread overview]
Message-ID: <200204100144.UAA05950@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Wed, 10 Apr 2002 00:17:16 +0200." <20020409221716.GI5148@atrey.karlin.mff.cuni.cz>
pavel@suse.cz said:
> Okay, make it /dev/urandom ;-).
Doesn't /dev/urandom have exactly the same DOS properties as /dev/random?
I.e. it reads real random numbers until the entropy pool is empty, then
starts returning pseudo-random numbers? If so, things on the host will
still hang when they then try to read /dev/random.
Also, UML processes deserve crytographically secure numbers just as much as
host proceses do. When something opens /dev/random, /dev/random is exactly
what it should get.
Jeff
next prev parent reply other threads:[~2002-04-10 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 20:56 user-mode port 0.56-2.4.18-15 Jeff Dike
2002-04-08 1:25 ` Pavel Machek
2002-04-09 23:16 ` Jeff Dike
2002-04-09 22:17 ` Pavel Machek
2002-04-10 1:44 ` Jeff Dike [this message]
2002-04-10 3:53 ` [uml-user] " Andreas Dilger
2002-04-10 21:14 ` David Wagner
2002-04-08 20:02 ` Robert Love
2002-04-08 23:09 ` Jeff Dike
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=200204100144.UAA05950@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=user-mode-linux-user@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