From: "Folkert van Heusden" <folkert@vanheusden.com>
To: "'John Bradford'" <john@grabjohn.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Want a random entropy source?
Date: Sat, 28 Dec 2002 21:53:17 +0100 [thread overview]
Message-ID: <004401c2aeb3$26c32f20$3640a8c0@boemboem> (raw)
In-Reply-To: <200212282039.gBSKdGWF001663@darkstar.example.net>
> Well, the 50hz from the mains isn't a perfect 50hz; it has random (yes)
> fluctuations.
JB> Yes, that's true.
JB> More generally, though, is there any point in this going in to the
JB> mainline kernel, if:
JB> * Most users don't need faster entropy generation than we've got
JB> and
JB> * The entropy gathered from the soundcard is statistically inferior to
JB> that gathered from the current sources of entropy.
Well, there isn't any :o) That's why there's a user-level implementation
for such a beast for those who do need it.
( http://www.vanheusden.com/mirrors/audio-entropyd-0.0.5.tgz )
JB> I don't see how it's possible to guarantee that the data below a
JB> certain dB level from the soundcard is noise.
Some guy contacted me about audio-entropyd and told me he'd done a lot
of analysis on all how this and gave me a few hints how to improve the
quality of what is produced with this tool. A quick fourier-
transformation doesn't really show any peaks.
next prev parent reply other threads:[~2002-12-28 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 16:16 two 2.5 modules bugs Mikael Pettersson
2002-12-27 23:24 ` Petr Vandrovec
2002-12-28 10:37 ` Rusty Russell
2002-12-28 15:40 ` Want a random entropy source? Stephen Satchell
2002-12-28 16:00 ` John Bradford
2002-12-28 16:38 ` Dr. David Alan Gilbert
2002-12-28 16:47 ` Russell King
2002-12-28 17:15 ` John Bradford
2002-12-28 20:28 ` Folkert van Heusden
2002-12-28 20:39 ` John Bradford
2002-12-28 20:53 ` Folkert van Heusden [this message]
2002-12-28 23:20 ` Stephen Satchell
2002-12-28 23:41 ` John Bradford
2002-12-28 20:27 ` Folkert van Heusden
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='004401c2aeb3$26c32f20$3640a8c0@boemboem' \
--to=folkert@vanheusden.com \
--cc=john@grabjohn.com \
--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
all inboxes | Powered by JetHome®