RE: OpenSSL thread safety (was: possibly bug in crypto/rand/rand_win.c)

2004-07-14 Thread Peter Waltenberg
the certified code begins and ends. Peter Steven Reddie [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/14/04 03:49 PM Please respond to openssl-dev To [EMAIL PROTECTED] cc Subject RE: OpenSSL thread safety (was: possibly bug in crypto/rand/rand_win.c) Hi Peter, Those

OpenSSL thread safety (was: possibly bug in crypto/rand/rand_win.c)

2004-07-13 Thread Steven Reddie
Hi Jeffrey, Come to think of it, maybe OpenSSL should simply perform a call to RAND_poll() as part of the DLL initialization. This would solve many problems. No, it would create some. RAND_poll() calls LoadLibrary() which is a no-no from DllMain(). malloc() is not safe to call from

Re: OpenSSL thread safety (was: possibly bug in crypto/rand/rand_win.c)

2004-07-13 Thread Peter Waltenberg
to support legacy systems where the shared lib initialization code just doesn't get called. Peter Steven Reddie [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/14/04 03:08 PM Please respond to openssl-dev To [EMAIL PROTECTED] cc Subject OpenSSL thread safety (was: possibly bug

RE: OpenSSL thread safety (was: possibly bug in crypto/rand/rand_win.c)

2004-07-13 Thread Steven Reddie
? -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter WaltenbergSent: Wednesday, 14 July 2004 3:26 PMTo: [EMAIL PROTECTED]Subject: Re: OpenSSL thread safety (was: possibly bug in crypto/rand/rand_win.c)1. It is safe to create/initialise