From: Prasanth Kumar <kumar1@home.com>
To: linux-kernel@vger.rutgers.edu
Subject: Re: /dev/random -- can I enlarge the `randomness stock'?
Date: Sun, 21 May 2000 17:06:11 -0700 [thread overview]
Message-ID: <392879F3.A4AA4104@home.com> (raw)
In-Reply-To: Pine.GSO.4.10.10005211917001.14371-100000@weyl.math.psu.edu
Alexander Viro wrote:
>
> On Sun, 21 May 2000, Alan Cox wrote:
>
> > > What if you simply tuned a cheap FM receiver to just static and fed
> > > that into a soundcard. Then reading from /dev/dsp or something would
> > > return pretty good random data, right ?
> >
> > An attacker with a radio transmitter...
>
> Faraday's cage + mic with a nasty loopback. The real problem being: you
> want a random data with known distribution and none of these methods will
> give that.
<snip>
Random number source by radioactive decay ;-)
http://www.fourmilab.ch/hotbits/
--
Prasanth Kumar
kumar1@home.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
parent reply other threads:[~2000-05-22 0:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.GSO.4.10.10005211917001.14371-100000@weyl.math.psu.edu>]
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=392879F3.A4AA4104@home.com \
--to=kumar1@home.com \
--cc=linux-kernel@vger.rutgers.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