From: Patrick Maupin <pmaupin@gmail.com>
To: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] time and random numbers
Date: Sat, 10 Mar 2012 19:48:32 -0600 [thread overview]
Message-ID: <CAPz3yKc=Q0nOpyv6uFRRY9VEHr3Y=z+GotDEZAPPQdPZU9H+rw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6OvFewXy3k0a7YSokuDEHHsujBvwDbfDBfbJ0g4Y3z4Q@mail.gmail.com>
On Sat, Mar 10, 2012 at 6:07 PM, Dave Taht <dave.taht@gmail.com> wrote:
> One of my other concerns in life is the lack of quality random numbers
> for use in cryptography.
Worth thinking about.
> http://warmcat.com/_wp/whirlygig-rng/
I'm not sure I would trust something like this unless I was sure the
author understood a lot of stuff about a lot of stuff, and that lots
of experts had then examined it from various aspects. There's a
growing body of literature on this. See, e.g.:
http://www.hindawi.com/journals/ijrc/2010/879281/
Having said that, the board I'm envisioning could actually be used for
the quantization stage of random number generation from random events
in time such as alpha decay.
next prev parent reply other threads:[~2012-03-11 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 0:07 Dave Taht
2012-03-11 1:48 ` Patrick Maupin [this message]
2012-03-12 15:21 ` Ron Frazier (NTP)
2012-03-12 21:05 ` Eric S. Raymond
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='CAPz3yKc=Q0nOpyv6uFRRY9VEHr3Y=z+GotDEZAPPQdPZU9H+rw@mail.gmail.com' \
--to=pmaupin@gmail.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
/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