Bodo Moeller wrote:
>
>
> I was suspicious about things like that -- and then there's this (now
> removed) note in INSTALL.W32 saying about the original SSLeay
> instructions that "some of this may be out of date and no longer
> applicable. In particular the Crypto_malloc_init() comment appears to
> be wrong: you always need to use the same runtime library as the DLL
> itself", which would mean that Crypto_malloc_init() is not needed
> after all. I recently asked for information on this but no-one
> replied.
>
Sorry I must have missed that message. I put that comment in. I can see
the logic behind CRYPTO_malloc_init() but I never got it to work myself.
I tested it by linking an app with a different runtime library than
OpenSSL was compiled with, calling CRYPTO_malloc_init() then trying to
do some things. It crashed almost immediately.
I can vaguely recall someone saying that if you linked with MFC then
this did work. I haven't tried that: I avoid Win32 development whenever
possible.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
