I'm using SSLeay for WIN32. I also use a program called BoundsChecker
from NuMega to check that all system resources are freed after use. When
executing my SSL application, BoundsChecker reports the following memory
leaks:
Memory leak: 2048 bytes allocated by malloc in crypto\lhash\lhash.c
(346), HANDLE: 0x025212F0
Memory leak: 20 bytes allocated by malloc in crypto\mem.c (146), HANDLE:
0x02530F90
Memory leak: 32 bytes allocated by malloc in crypto\mem.c (153), HANDLE:
0x02530FD0
Memory leak: 12 bytes allocated by malloc in crypto\lhash\lhash.c (201),
HANDLE: 0x02531160
Memory leak: 92 bytes allocated by malloc in crypto\lhash\lhash.c (129),
HANDLE: 0x02531540
Am I using SSLeay in the wrong way, or does BoundsChecker lie? I'm
basically doing the following:
SSL_CTX* pCtx;
SSLeay_add_ssl_algorithms();
SSL_load_error_strings();
pCtx = SSL_CTX_new(SSLv23_server_method());
SSL_CTX_use_certificate_file(pCtx,
"c:\\projekt\\cert\\proxy-cert.pem", SSL_FILETYPE_PEM);
SSL_CTX_use_RSAPrivateKey_file(pCtx,
"c:\\projekt\\cert\\proxy-key.pem", SSL_FILETYPE_PEM);
SSL_CTX_free(pCtx);
--
Tomas Hellberg, SECTRA, http://www.sectra.se/
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
