From: Andreas Dilger <adilger@clusterfs.com>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: henrique <henrique@cyclades.com>, linux-kernel@vger.kernel.org
Subject: Re: Problem with random.c and PPC
Date: Sat, 17 Aug 2002 00:05:07 -0600 [thread overview]
Message-ID: <20020817060507.GM9642@clusterfs.com> (raw)
In-Reply-To: <20020817004520.GN5418@waste.org>
On Aug 16, 2002 19:45 -0500, Oliver Xymoron wrote:
> Realistically, the hashing done by /dev/urandom is probably strong
> enough for most purposes. It's as cryptographically strong as whatever
> block cipher you're likely to use with it. /dev/random goes one step
> further and tries to offer something that's theoretically
> unbreakable. Useful for generating things like large public keys, less
> useful for generating the session keys used by SSL and the
> like. They're easier to break by direct attack.
One of the problems, I believe, is that reading from /dev/urandom will
also deplete the entropy pool, just like reading from /dev/random.
The only difference is that when the entropy is gone /dev/random will
stop and /dev/urandom will continue to provide data.
If you are in there fixing things, it might make sense to have
/dev/urandom extract entropy from the random pool far less often than
/dev/random. This way people who use /dev/urandom for a source of
less-strong randomness (e.g. TCP sequence numbers or whatever), will
not be shooting themselves in the foot for when they need a 2048-byte
PGP key, if they are low on entropy sources.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-08-17 6:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 10:00 Problem with random.c and PPC Jon Burgess
2002-08-16 19:52 ` Oliver Xymoron
2002-08-16 17:51 ` henrique
2002-08-16 21:21 ` Ruth Ivimey-Cook
2002-08-17 0:47 ` Oliver Xymoron
2002-08-17 0:45 ` Oliver Xymoron
2002-08-17 6:05 ` Andreas Dilger [this message]
2002-08-17 7:23 ` Oliver Xymoron
2002-08-17 9:09 ` Andreas Dilger
2002-08-17 16:56 ` Oliver Xymoron
2002-08-19 9:29 ` Marco Colombo
2002-08-19 14:02 ` Oliver Xymoron
2002-08-19 15:11 ` Marco Colombo
2002-08-19 15:29 ` Oliver Xymoron
2002-08-19 16:20 ` Marco Colombo
2002-08-19 16:33 ` Oliver Xymoron
2002-08-19 20:23 ` Marco Colombo
2002-08-22 3:16 ` David Wagner
2002-08-16 20:52 ` Chris Friesen
2002-08-17 0:29 ` Oliver Xymoron
2002-08-22 3:19 ` David Wagner
2002-08-22 15:40 ` Chris Friesen
2002-08-22 17:25 ` Remco Post
-- strict thread matches above, loose matches on Subject: below --
2002-08-15 16:10 henrique
2002-08-15 15:14 henrique
2002-08-15 18:25 ` Andreas Dilger
2002-08-15 19:03 ` Tom Rini
2002-08-15 19:59 ` Andreas Dilger
2002-08-15 21:04 ` Tom Rini
2002-08-16 1:50 ` H. Peter Anvin
2002-08-16 16:33 ` Oliver Xymoron
2002-08-16 16:28 ` Oliver Xymoron
[not found] ` <20020816170126.GD26993@opus.bloom.county>
2002-08-16 17:15 ` Oliver Xymoron
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=20020817060507.GM9642@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=henrique@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.org \
/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