From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
To: cypherpunks@toad.com
Message Hash: db2b27833f4c5628505eaaf4f49175634576d9902851dff688a7f932c39191e3
Message ID: <9404180409.AA16376@anchor.ho.att.com>
Reply To: N/A
UTC Datetime: 1994-04-18 04:10:58 UTC
Raw Date: Sun, 17 Apr 94 21:10:58 PDT
From: wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)
Date: Sun, 17 Apr 94 21:10:58 PDT
To: cypherpunks@toad.com
Subject: Re: rng, anyone?
Message-ID: <9404180409.AA16376@anchor.ho.att.com>
MIME-Version: 1.0
Content-Type: text/plain
Eric et al write:
> >> There is a problem with generating random numbers by repeated
> >> iterations of a hash function when these numbers will be used to
> >> simulate an encrypted message body.
> >Try xoring the output with a secret value between MD5 hashes.
> That'll work. Take the seed as the secret value, and take the first
> hash as the first block.
Or you can delete some bits from the MD5, or, since MD5 takes more input
than it gives output, append a secret value to the MD5 before rehashing.
Return to April 1994
Return to “wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)”
1994-04-18 (Sun, 17 Apr 94 21:10:58 PDT) - Re: rng, anyone? - wcs@anchor.ho.att.com (bill.stewart@pleasantonca.ncr.com +1-510-484-6204)