From: daw@mozart.cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: /dev/random in 2.4.6
Date: 19 Aug 2001 17:32:42 GMT [thread overview]
Message-ID: <9lot7q$pmg$4@abraham.cs.berkeley.edu> (raw)
In-Reply-To: <20010817171834.A24850@thunk.org> <NOEJJDACGOHCKNCOGFOMKEFFDEAA.davids@webmaster.com> <20010819111357.A3504@thunk.org>
Theodore Tso wrote:
>On Fri, Aug 17, 2001 at 03:05:39PM -0700, David Schwartz wrote:
>> This is a non-issue providing the entropy pool code correctly
>> estimates the amount of entropy. The Linux entropy code is written
>> so that there is no harm from putting fully known or partially known
>> numbers into the pool provided that the pool does not overestimate
>> the amount of entropy in those numbers.
>
>The problem is that by being able to perfectly observe packets on the
>LAN, you know a lot more about the numbers that are going in, and it's
>therefore extremely likely that the entropy estimate will be
>overestimated.
Right. Therefore, it seems to me that the correct thing to do is to
add network timings into the pool using an entropy estimate of zero.
next prev parent reply other threads:[~2001-08-19 17:36 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 15:07 /dev/random in 2.4.6 Steve Hill
2001-08-15 15:21 ` Richard B. Johnson
2001-08-15 15:27 ` Steve Hill
2001-08-15 15:42 ` Richard B. Johnson
2001-08-15 16:29 ` Tim Walberg
2001-08-15 17:13 ` Andreas Dilger
2001-08-16 8:37 ` Steve Hill
2001-08-16 19:11 ` Andreas Dilger
2001-08-16 19:35 ` Alex Bligh - linux-kernel
2001-08-16 20:30 ` Andreas Dilger
2001-08-17 0:49 ` Robert Love
2001-08-17 1:05 ` Robert Love
2001-08-19 17:29 ` David Wagner
2001-08-17 21:18 ` Theodore Tso
2001-08-17 22:05 ` David Schwartz
2001-08-19 15:13 ` Theodore Tso
2001-08-19 15:33 ` Rob Radez
2001-08-19 17:32 ` David Wagner [this message]
2001-08-19 23:32 ` Oliver Xymoron
2001-08-20 7:40 ` Helge Hafting
2001-08-20 14:01 ` Oliver Xymoron
2001-08-20 13:37 ` Alex Bligh - linux-kernel
2001-08-20 14:12 ` Oliver Xymoron
2001-08-20 14:40 ` Alex Bligh - linux-kernel
2001-08-20 14:55 ` Chris Friesen
2001-08-20 15:22 ` Oliver Xymoron
2001-08-20 15:25 ` Doug McNaught
2001-08-20 15:42 ` Chris Friesen
2001-08-21 10:03 ` Steve Hill
2001-08-21 18:14 ` David Wagner
2001-08-20 16:01 ` David Wagner
2001-08-20 19:30 ` Gérard Roudier
2001-08-20 15:07 ` Oliver Xymoron
2001-08-21 8:33 ` Alex Bligh - linux-kernel
2001-08-21 16:13 ` Oliver Xymoron
2001-08-21 17:44 ` Alex Bligh - linux-kernel
2001-08-21 18:24 ` David Wagner
2001-08-21 18:49 ` Alex Bligh - linux-kernel
2001-08-21 19:04 ` Oliver Xymoron
2001-08-21 19:20 ` Alex Bligh - linux-kernel
2001-08-21 21:44 ` Robert Love
2001-08-21 18:19 ` David Wagner
2001-08-20 16:00 ` David Wagner
2001-08-21 1:20 ` Theodore Tso
2001-08-21 8:39 ` Alex Bligh - linux-kernel
2001-08-21 10:46 ` Marco Colombo
2001-08-21 12:40 ` Alex Bligh - linux-kernel
2001-08-21 17:06 ` cfs+linux-kernel
2001-08-21 17:48 ` Alex Bligh - linux-kernel
2001-08-21 18:27 ` David Wagner
2001-08-21 18:25 ` David Wagner
2001-08-20 22:55 ` D. Stimits
2001-08-21 1:06 ` David Schwartz
2001-08-19 17:31 ` David Wagner
2001-08-19 17:27 ` David Wagner
2001-08-15 19:25 ` Alex Bligh - linux-kernel
2001-08-15 20:55 ` Robert Love
2001-08-15 21:27 ` Alex Bligh - linux-kernel
2001-08-16 8:55 ` Steve Hill
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='9lot7q$pmg$4@abraham.cs.berkeley.edu' \
--to=daw@mozart.cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.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