1995-09-19 - Verification of Random Number Generators

Header Data

From: “Erik E. Fair” (Time Keeper) <fair@clock.org>
To: Eric Young <jsw@neon.netscape.com>
Message Hash: 7f3ed16e3dcfd9e4b465f49065f5e910f19b95ce5614458fb9b592cc628dd3ef
Message ID: <v02110102ac849090d9fe@[17.255.9.110]>
Reply To: N/A
UTC Datetime: 1995-09-19 16:04:52 UTC
Raw Date: Tue, 19 Sep 95 09:04:52 PDT

Raw message

From: "Erik E. Fair"  (Time Keeper) <fair@clock.org>
Date: Tue, 19 Sep 95 09:04:52 PDT
To: Eric Young <jsw@neon.netscape.com>
Subject: Verification of Random Number Generators
Message-ID: <v02110102ac849090d9fe@[17.255.9.110]>
MIME-Version: 1.0
Content-Type: text/plain


At 2:20 9/19/95, Eric Young wrote:

>Now I had not noticed this, my library runs like a charm and things
>appear random from the random number generator.  This sort of error can
>only be checked by reading the code and specifically looking at critical
>routines like this the RNG seeding routines.  The advantage of my code
>being public is that some-one like Mike can have a look and pick up
>problems like this.
>The moral of the story I suppose is to be
>paranoid about checking routines relating to RNG.

Just an idle thought: it might be possible to do a probabalistic
verification of a RNG by sampling it over some number of samples, and
statistically analyzing the sample space. This would be analysis under the
model of "RNG as black box" as opposed to (or rather, if you're smart, in
addition to) code inspection & review. Any statisticians among us?

Erik Fair







Thread