From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Interesting research possibility?
Date: Tue, 25 Jun 2002 16:23:10 -0400 [thread overview]
Message-ID: <9802e5350f20713ff27cf0be630c9fbf@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]
That's essentially how we use /dev/random in the security library. I wouldn't mind
replacing the current seeding with something a little more trustworthy. I'm afraid
that beating the cpu clock against the interrupt one will eventually fail because
they'll end up being the same crystal on some system. On some architectures, like our
SGI's they already are.
[-- Attachment #2: Type: message/rfc822, Size: 1760 bytes --]
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Interesting research possibility?
Date: Tue, 25 Jun 2002 15:59:46 -0400
Message-ID: <200206251959.PAA19776@math.psu.edu>
> I had a few that I used to run at it every now and then; self correlation,
> and a random quadrant walk. Haven't in a while. I'll fix them up and stick
> them out there. We could always use more.
What about doing Yarrow and seeding it with random thermal noise?
- Dan C.
http://www.counterpane.com/yarrow-notes.html
next reply other threads:[~2002-06-25 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 20:23 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-25 18:08 presotto
2002-06-25 19:59 ` Dan Cross
2002-06-25 17:59 rog
2002-06-25 17:42 presotto
2002-06-25 17:17 ozan s. yigit
2002-06-25 15:19 rog
2002-06-25 14:54 ` Sam
2002-06-24 13:24 Sam
2002-06-24 15:28 ` andrey mirtchovski
2002-06-24 19:48 ` Chris Hollis-Locke
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=9802e5350f20713ff27cf0be630c9fbf@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).