public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Roland Dreier <roland@topspincom.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Continuing /dev/random problems with 2.4
Date: 04 Feb 2002 17:45:27 -0500	[thread overview]
Message-ID: <1012862738.848.95.camel@phantasy> (raw)
In-Reply-To: <52n0yolvpt.fsf@love-boat.topspincom.com>
In-Reply-To: <Pine.LNX.3.96.1020204171035.31056A-100000@gatekeeper.tmr.com>  <52n0yolvpt.fsf@love-boat.topspincom.com>

On Mon, 2002-02-04 at 17:37, Roland Dreier wrote:

> Entropy is gathered from interrupt timing in the kernel because
> interrupts are handled in the kernel.  It would be quite difficult for
> a user space process to get accurate information about interrupt
> timing.
> 
> However, the i8xx RNG and audio entropy daemons work perfectly well
> from user space.  What is gained by moving that code into the kernel?

Exactly.  Nothing is gained.

A misconception in this thread seems to be on how this works. 
Generating entropy from interrupts and block I/O uses timing values. 
Differences in successive operations of whatever.  The infrastructure
for carrying out those operations already exists, we just need to note
their timing. 

The i8xx and other RNGs are different.  They actually _give_ us the
random data.  In other words, they generate entropy to just push
directly into the pool.  The concern is that this data may not be safe,
and thus we need to run a fitness test on it (i.e. FIPS 190, I
believe).  All this muck is new code and can exist in userspace --
therefore it will.

	Robert Love


  reply	other threads:[~2002-02-04 22:46 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  9:17 Continuing /dev/random problems with 2.4 Ken Brownfield
2002-02-01 16:36 ` Andreas Dilger
2002-02-01 17:00   ` Ken Brownfield
2002-02-01 16:53 ` Robert Love
2002-02-01 17:01   ` Ken Brownfield
2002-02-04  9:28     ` Sean Hunter
2002-02-01 18:40   ` H. Peter Anvin
2002-02-01 19:38     ` Ken Brownfield
2002-02-01 19:50       ` Robert Love
2002-02-01 19:52         ` Ken Brownfield
2002-02-01 19:57       ` Andreas Dilger
2002-02-01 20:22         ` Ken Brownfield
2002-02-01 19:43     ` Andreas Dilger
2002-02-01 20:12       ` H. Peter Anvin
2002-02-01 20:28         ` Jeff Garzik
2002-02-02  1:33           ` David Wagner
2002-02-02  8:01             ` Jeff Garzik
2002-02-02  8:54           ` Kai Henningsen
2002-02-02 11:13             ` Andreas Dilger
2002-02-04 22:13         ` Bill Davidsen
2002-02-04 22:37           ` Roland Dreier
2002-02-04 22:45             ` Robert Love [this message]
2002-02-05 23:02               ` Bill Davidsen
2002-02-05 23:17                 ` Robert Love
2002-02-06 16:16                   ` Bill Davidsen
2002-02-06 16:31                     ` Need a clew WRT fig2dev Kirk Reiser
2002-02-06 16:42                       ` Adrian Bunk
2002-02-06 20:40                       ` Jeff Garzik
2002-02-09 19:45                     ` Continuing /dev/random problems with 2.4 Nix N. Nix
2002-02-03 12:51       ` Henning P. Schmiedehausen
2002-02-01 20:23     ` Peter Monta
2002-02-01 20:27       ` H. Peter Anvin
2002-02-01 20:36         ` Jeff Garzik
2002-02-01 20:33       ` Jeff Garzik
2002-02-01 20:40         ` H. Peter Anvin
2002-02-01 20:54           ` Jeff Garzik
2002-02-01 20:56         ` Peter Monta
2002-02-01 22:54           ` H. Peter Anvin
2002-02-01 23:27             ` Peter Monta
2002-02-02  1:50               ` H. Peter Anvin
2002-02-02  2:05       ` David Wagner
2002-02-02  3:30         ` Peter Monta
2002-02-02 21:02         ` Martin Dalecki
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 21:53 Ishan O. Jayawardena

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=1012862738.848.95.camel@phantasy \
    --to=rml@tech9.net \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@topspincom.com \
    /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