From: Oliver Xymoron <oxymoron@waste.org>
To: David Schwartz <davids@webmaster.com>
Cc: cfriesen@nortelnetworks.com, Alexander Viro <viro@math.psu.edu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Entropy from disks
Date: Tue, 5 Nov 2002 18:27:08 -0600 [thread overview]
Message-ID: <20021106002708.GA25611@waste.org> (raw)
On Tue, Nov 05, 2002 at 03:55:57PM -0800, David Schwartz wrote:
>
> On Tue, 29 Oct 2002 13:02:39 -0500, Chris Friesen wrote:
> >Oliver Xymoron wrote:
>
> >I'm not an expert in this field, so bear with me if I make any blunders
> >obvious to one trained in information theory.
>
> >>The current Linux PRNG is playing fast and loose here, adding entropy
> >>based on the resolution of the TSC, while the physical turbulence
> >>processes that actually produce entropy are happening at a scale of
> >>seconds. On a GHz processor, if it takes 4 microseconds to return a
> >>disk result from on-disk cache, /dev/random will get a 12-bit credit.
>
> >In the paper the accuracy of measurement is 1ms. Current hardware has
> >tsc precision of nanoseconds, or about 6 orders of magnitude more
> >accuracy. Doesn't this mean that we can pump in many more bits into the
> >algorithm and get out many more than the 100bits/min that the setup in
> >the paper acheives?
>
> In theory, if there's any real physical randomness in a timing source, the
> more accuracy you measure the timing to, the more bits you get.
Not if the timing source is clocked at a substantially slower speed
than the measurement clock and is phase locked. Which is the case.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
next reply other threads:[~2002-11-06 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 0:27 Oliver Xymoron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-29 17:10 Entropy from disks Oliver Xymoron
2002-10-29 18:02 ` Chris Friesen
2002-10-29 19:08 ` Oliver Xymoron
2002-11-05 23:55 ` David Schwartz
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=20021106002708.GA25611@waste.org \
--to=oxymoron@waste.org \
--cc=cfriesen@nortelnetworks.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.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