On Mon, Aug 28, 2000 at 01:43:05PM -0400, Allen Smith wrote:
> > The Yarrow API is different from other PRNGs in that it differenciates
> > between different randomness sources. That means that applications
> > must call the Yarrow_Input function directly, or the OpenSSL API
> > (RAND_add() and RAND_METHOD) would have to be modified to reflect
> > this.
>
> BTW, I'm currently working on a parallel project, namely incorporating
> many of Yarrow's improvements (e.g., fast/slow pools) into EGD, plus
> other improvements to EGD (including ones that eliminate the problems
> with running out of entropy even if you're only needing low-quality
> entropy). I should have a testing version ready pretty soon, although
> there are a lot more improvements that need to be made in it. I'm
> mentioning this on the OpenSSL list because some of the improvements
> in question will enable OpenSSL to work better with EGD; I've done
> some work on rewriting rand_egd.c for this, although that needs
> further testing (I'm much more of a Perl programmer than I am a C
> programmer, which is one reason why EGD interests me...).
I see with great pleasure that the number of choices available for those
people without /dev/urandom in their OS is going to increase in the
near future.
You write about changes in rand_egd.c, I assume you nevertheless try to
maintain compatibility to the EGD interface.
I might have a look into your rand_egd.c changes, I don't don't have the
slightest clue of Perl, though :-) (So in a certain sense we complement
each other :-))
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cottbus Fax. +49 355 69-4153
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
