Notice to Sender
================

This message was received by this installation but could not be
delivered to its intended cc:Mail recipient(s).

  Original subject: Net::SSLeay and RAND_seed bug?

Intended recipient(s) who DID NOT receive this message:

  [EMAIL PROTECTED]

The following cc:Mail error(s) were recorded:

  ***  Message recipient is unknown  ***


-------- Original Message Text --------
Hi all

I've run into a problem with Net::SSLeay::RAND_seed($buf).

I'm working on WinNT4 with Net::SSLeay 1.05 and OpenSSL 0.9.5.
(I'll be posting instructions how to get those two to work together on NT as 
soon as the Net::SSLeay homepage is up again)

Since OpenSSL 0.9.5 complains when the PRNG is not seeded I'm using RAND_seed 
to provide some initial data. Because this didn't seem to help while debugging 
my perl scripts I built debug versions of Net::SSLeay and OpenSSL and tried to 
track it down. 

I found that <openssl>/crypto/rand/rand_lib.c/RAND_seed(const void *buf, int 
num) ALWAYS gets called with a buffer pointing to the value 
"*Net::SSLeay::RAND_seed" and num = 23!!! (Except when run in the ActiveState 
debugger; then the buffer always points to "10000" and num=5, which is 
definetely to few bytes, so OpenSSL complains).

There seems to be a problem with the interface from Net::SSLeay::RAND_seed() to 
OpenSSL:RAND_seed(). Does anybody know how to fix this?


Thanks Marcel

(PS: Sampo, is there any Net::SSLeay 1.0.6 in the queue?)

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to