All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Hunter <sean@dev.sportingbet.com>
To: Ken Brownfield <brownfld@irridia.com>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>,
	"Proescholdt, timo" <Timo.Proescholdt@brk-muenchen.de>,
	linux-kernel@vger.kernel.org
Subject: Re: randomness - compaq smart array driver
Date: Wed, 13 Feb 2002 15:08:50 +0000	[thread overview]
Message-ID: <20020213150850.H26054@dev.sportingbet.com> (raw)
In-Reply-To: <410B51F29EA8D3118EE400508B44AE2B3C6FB3@RZ_NT_MAIL> <Pine.LNX.4.33.0202111754560.5685-100000@gans.physik3.uni-rostock.de> <20020213071445.A20717@asooo.flowerfire.com>
In-Reply-To: <20020213071445.A20717@asooo.flowerfire.com>; from brownfld@irridia.com on Wed, Feb 13, 2002 at 07:14:45AM -0600

On Wed, Feb 13, 2002 at 07:14:45AM -0600, Ken Brownfield wrote:
> Yes, I've been using the netdev patches for months.  Aside from the
> unrelated entropy exhaustion bug, his patches are stable (and optional)
> and help on diskless or low-I/O machines.  2.4 or 2.5 anyone? :)

Randomness from network packet timings can be gathered entirely in userspace by
using a packet socket.  I am busy writing an "additional entropy daemon" to
gather entropy from this and other sources[1], clean it up, test its fitness,
estimate its information content, and feed it into the random pool.  This job
is (IMO) better done in userspace because there we can run fitness tests on the
stream more easily because we have floating point etc.

I personally don't think that network packet timings should be added to the
entropy pool by the kernel because they could be controlled to a lesser or
greater extent by an attacker.  I'm hoping that the fitness tests in my
userspace thingy would detect this.

Sean

[1] Including clock jitter and soundcard noise (I got the idea
    from Schneier 1996).

  reply	other threads:[~2002-02-13 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11 15:00 randomness - compaq smart array driver Proescholdt, timo
2002-02-11 16:58 ` Tim Schmielau
2002-02-13 13:14   ` Ken Brownfield
2002-02-13 15:08     ` Sean Hunter [this message]
2002-02-13 15:49       ` Chris Friesen
  -- strict thread matches above, loose matches on Subject: below --
2002-02-11 17:41 Stephen Cameron

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=20020213150850.H26054@dev.sportingbet.com \
    --to=sean@dev.sportingbet.com \
    --cc=Timo.Proescholdt@brk-muenchen.de \
    --cc=brownfld@irridia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.