public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Robert Love <rml@ufl.edu>, David Wagner <daw@mozart.cs.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Allow net devices to contribute to /dev/random
Date: Mon, 1 Oct 2001 16:43:54 +0200	[thread overview]
Message-ID: <20011001164354.A21715@bug.ucw.cz> (raw)
In-Reply-To: <1001461026.9352.156.camel@phantasy> <9or70g$i59$1@abraham.cs.berkeley.edu> <1001465531.10701.61.camel@phantasy>
In-Reply-To: <1001465531.10701.61.camel@phantasy>; from Robert Love on Tue, Sep 25, 2001 at 08:52:09PM -0400

Hi!

> > Here is my reasoning.  I'd like to quote drivers/char/random.c:
> >   * add_interrupt_randomness() uses the inter-interrupt timing as random
> >   * inputs to the entropy pool.  Note that not all interrupts are good
> >   * sources of randomness!  For example, the timer interrupts is not a
> >   * good choice, because the periodicity of the interrupts is too
> >   * regular, and hence predictable to an attacker.  Disk interrupts are
> >   * a better measure, since the timing of the disk interrupts are more
> >   * unpredictable.
> >   * 
> >   * All of these routines try to estimate how many bits of randomness a
> >   * particular randomness source.  They do this by keeping track of the
> >   * first and second order deltas of the event timings.
> 
> Obviously the timer interrupt would be the worst idea ever.  Its the
> same value (HZ) on almost all versions of Linux (Alpha being on example
> where it is not the same).

Actually, not quite. On 2.4.9 system, console kept interrupts disabled
for so long that timer interrupt was pretty good source of randomness.

								Pavel
-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

  parent reply	other threads:[~2001-10-01 20:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 23:36 [PATCH][RFC] Allow net devices to contribute to /dev/random Robert Love
2001-09-26  0:20 ` David Wagner
2001-09-26  0:52   ` Robert Love
2001-09-26  1:36     ` David Wagner
2001-09-26 22:55       ` Gordon Oliver
2001-09-26 23:06         ` Andreas Steinmetz
2001-09-26 15:49     ` dean gaudet
2001-09-26 17:00     ` Oliver Xymoron
2001-10-01 14:43     ` Pavel Machek [this message]
2001-10-01 21:33       ` Robert Love
2001-10-01  9:52   ` Florian Weimer
2001-10-01 16:59     ` /dev/random entropy calculations broken? Andreas Dilger
2001-10-01 21:55       ` Alex Bligh - linux-kernel
2001-10-01 22:43         ` antirez
2001-10-02  7:51       ` Andreas Dilger
2001-10-02  8:10         ` Andreas Dilger
2001-10-02 15:37         ` Oliver Xymoron
2001-10-02 21:02           ` Andreas Dilger
2001-10-02 21:29             ` Oliver Xymoron
2001-10-02 22:28               ` Andreas Dilger
2001-10-19 22:59         ` [PATCH] " Andreas Dilger
2001-10-21  5:05           ` Robert Love

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=20011001164354.A21715@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=daw@mozart.cs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ufl.edu \
    /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