In article <> you wrote: > I solved the "nonexissting" .dll problem by adding: > CRYPTO_malloc_init(malloc,realloc,free) before calling > any SSL-methods. > as documented in the header file.... crypto.h from the > SSLeay distribution: Oh, interesting and good to know. Is the following patch correct, i.e. is this enouch "before": :> cvs diff ssl_engine_init.c Index: ssl_engine_init.c =================================================================== RCS file: /e/apache/SSL/REPOS/mod_ssl/pkg.apache/src/modules/ssl/ssl_engine_init.c,v retrieving revision 1.15 diff -u -r1.15 ssl_engine_init.c --- ssl_engine_init.c 1998/09/24 14:10:40 1.15 +++ ssl_engine_init.c 1998/10/08 15:42:24 @@ -113,6 +113,9 @@ * initialize SSLeay (already needed for the pass phrase dialog) */ ssl_log(s, SSL_LOG_INFO, "Init: Initializing SSLeay library"); +#ifdef WIN32 + CRYPTO_malloc_init(malloc, realloc, free); +#endif SSL_load_error_strings(); SSLeay_add_ssl_algorithms(); Now we only need some hints/patches from you on how to build mod_ssl as a DLL (especially the .EXP stuff and the used commands and flags). Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
