1995-09-21 - Re: (none)

Header Data

From: Eric Young <eay@mincom.oz.au>
To: “James A. Donald” <jamesd@echeque.com>
Message Hash: 989ff2d670c4dcb53c2c6d7922bc9feb45123a4526eed59ab9026d9e219423a5
Message ID: <Pine.SOL.3.91.950921165214.28008A-100000@orb>
Reply To: <199509210627.XAA14935@blob.best.net>
UTC Datetime: 1995-09-21 07:10:32 UTC
Raw Date: Thu, 21 Sep 95 00:10:32 PDT

Raw message

From: Eric Young <eay@mincom.oz.au>
Date: Thu, 21 Sep 95 00:10:32 PDT
To: "James A. Donald" <jamesd@echeque.com>
Subject: Re: (none)
In-Reply-To: <199509210627.XAA14935@blob.best.net>
Message-ID: <Pine.SOL.3.91.950921165214.28008A-100000@orb>
MIME-Version: 1.0
Content-Type: text/plain


On Wed, 20 Sep 1995, James A. Donald wrote:
> However the algorithm I described simply used less computation, but the
> overhead of continually doing MD5 is probably modest. 

On a 486DX50 Solaris 2.4 I can do about 40,000 md5's per second.
(if input is < 56 bytes and contiguious).

With an mixing algorithm this fast, you could use it once per 
byte and still have an acceptable RNG.
It is definitly my hash function of choice :-).

eric
--
Eric Young                  | Signature removed since it was generating
AARNet: eay@mincom.oz.au    | more followups than the message contents :-)






Thread