linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sandy Harris <sandy@storm.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] frandom - fast random generator module
Date: Wed, 22 Oct 2003 11:49:02 +0800	[thread overview]
Message-ID: <3F95FE2E.7000404@storm.ca> (raw)
In-Reply-To: <bn4l5q$v73$1@cesium.transmeta.com>

H. Peter Anvin wrote:

> No, I mean that putting a piece of code in the kernel "so it can be
> accessed from shell scripts" is idiotic.  Make a binary of it and put
> it in the filesystem.

I posted one of those here during a previous discussion.
http://www.geocrawler.com/archives/3/35/2000/8/0/4192943/
The version I posted was first draft code, quite likely buggy,
but the general idea  was sound.

This was a while back, before the /dev/random code was
rewritten into a two-stage generator. Since my code
was to add a second stage to old /dev/random, I doubt it
is now a good idea.

If the problem is that /dev/urandom is too slow, then
we need to look at speeding it up, not adding a PRNG,
let alone one in the kernel.

Would a block cipher second stage as in Yarrow or my
example be faster than the hashing 2nd stage Ted used?
Can we use a block cipher without legal hassles? Is
there some third choice? A faster hash?


  parent reply	other threads:[~2003-10-22  3:46 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16  8:22 [RFC] frandom - fast random generator module Eli Billauer
2003-10-16  8:36 ` Nick Piggin
2003-10-16 10:20   ` Eli Billauer
2003-10-16 10:48     ` Nick Piggin
2003-10-16 11:29     ` Jeff Garzik
2003-10-16 12:27       ` Eli Billauer
2003-10-16 15:10         ` Jeff Garzik
2003-10-16 16:20       ` Andreas Dilger
2003-10-16 16:31         ` Jeff Garzik
2003-10-16 18:18           ` Andreas Dilger
2003-10-16 18:52             ` Richard B. Johnson
2003-10-16 19:31             ` Matt Mackall
2003-10-16 20:40               ` Andreas Dilger
2003-10-16 21:03             ` David Wagner
2003-10-16 23:17             ` Jeff Garzik
2003-10-16 23:42               ` Andreas Dilger
2003-10-17  0:34                 ` David Wagner
2003-10-16 17:45         ` Matt Mackall
2003-10-16 18:38           ` Andreas Dilger
2003-10-16 19:08             ` Matt Mackall
2003-10-16 20:27               ` Andreas Dilger
2003-10-16 20:37                 ` Matt Mackall
2003-10-16 17:31       ` Matt Mackall
2003-10-16 23:03         ` Eli Billauer
2003-10-16 23:07           ` Jeff Garzik
2003-10-16 23:13           ` Matt Mackall
2003-10-16 23:35           ` jw schultz
2003-10-21 19:24       ` bill davidsen
2003-10-21 19:55       ` bill davidsen
2003-10-21 21:21         ` Helge Hafting
2003-10-21 22:18           ` bill davidsen
2003-10-22  1:04             ` H. Peter Anvin
2003-10-21 19:17   ` bill davidsen
2003-10-21 21:00     ` H. Peter Anvin
2003-10-21 22:08       ` bill davidsen
2003-10-22  1:06         ` H. Peter Anvin
2003-10-22  2:56           ` jw schultz
2003-10-22 16:22             ` Kent Borg
2003-10-23  2:46               ` Dale Farnsworth
2003-10-23  3:22               ` Sandy Harris
2003-10-23 14:15                 ` Kent Borg
2003-10-24 17:37                 ` bill davidsen
2003-10-24 17:54                   ` Theodore Ts'o
2003-10-24 20:59                   ` David Wagner
2003-10-24 21:33                     ` jw schultz
2003-10-22  3:49           ` Sandy Harris [this message]
2003-10-16 10:45 ` Ingo Oeser
2003-10-21 19:30   ` bill davidsen
     [not found] <HbGf.8rL.1@gated-at.bofh.it>
     [not found] ` <HbQ5.ep.27@gated-at.bofh.it>
     [not found]   ` <Hdyv.2Vd.13@gated-at.bofh.it>
     [not found]     ` <HeE6.4Cc.1@gated-at.bofh.it>
     [not found]       ` <HjaT.3nN.7@gated-at.bofh.it>
     [not found]         ` <Hjkw.3Al.11@gated-at.bofh.it>
2003-10-16 17:46           ` David Mosberger-Tang
2003-10-16 19:28             ` Eli Billauer
2003-10-16 20:42               ` Andreas Dilger
2003-10-21 19:46                 ` bill davidsen
2003-10-16 21:30               ` Matt Mackall

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=3F95FE2E.7000404@storm.ca \
    --to=sandy@storm.ca \
    --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;
as well as URLs for NNTP newsgroup(s).