public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: Steve Hill <steve@navaho.co.uk>,
	"Richard B. Johnson" <root@chaos.analogic.com>,
	linux-kernel@vger.kernel.org
Subject: Re: /dev/random in 2.4.6
Date: Thu, 16 Aug 2001 14:30:58 -0600	[thread overview]
Message-ID: <20010816143058.Z31114@turbolinux.com> (raw)
In-Reply-To: <20010816131112.V31114@turbolinux.com> <212844030.997994112@[169.254.45.213]>
In-Reply-To: <212844030.997994112@[169.254.45.213]>

On Thu, Aug 16, 2001 at 08:35:12PM +0100, Alex Bligh - linux-kernel wrote:
> It's a while since I looked, but I /thought/ entropy only came from
> IDE (not for instance from SCSI, and certainly not when everything
> is sitting in cache). I have a reasonably active mailserver (SCSI,
> no k/b, no mouse, lots of RAM) which doesn't have enough entropy
> to cope with SSL/TLS gracefully without relying on the network
> traffic (i.e. behaves like it is ramdisk only).

Actually, AFAIK you _may_ get entropy from the IDE interrupts directly
(I didn't check), but you also appear to get entropy from block I/O
completions as well.  I _thought_ I had seen such lines in IDE, DAC960,
and also in the SCSI midlayer, but then I wasn't paying much attention
to those - I was trying to track down the interrupts for net devices.

If it is NOT in the SCSI block I/O layer, it should probably be added.
Whether it makes sense to have entropy from both the block layer and
the actual device IRQs is an issue left up to the security experts (it
may have correlation, and not be good entropy).

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


  reply	other threads:[~2001-08-16 20:31 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 [this message]
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
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=20010816143058.Z31114@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=linux-kernel@alex.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=steve@navaho.co.uk \
    /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