Hi all,
The Memory leak is reported after the connection is closed and after I free
the memory. In order to test it I have written a code for calling the SSL_accept()
function twice. But when I try to link to the SSL library it doesnot work. If any
sample code is there for testing can a
Selon "Dr. Stephen Henson" <[EMAIL PROTECTED]>:
> In this case I suspect that CRYPTO_cleanup_all_ex_data() should be called
> because calling RSA_new() will allocate an internal ex_data table.
Thank you, that's what i was searching for.
Sorry for disturbing and thank you all for this great work.
On Fri, Jul 30, 2004, Jim Schneider wrote:
> This seems to be a rather fruitful perennial on this mailing list. Do we have
> a FAQ we can add this one to?
>
> The general consensus seems to be: Before you ask about a memory leak in the
> OpenSSL libraries, try doing your complete cycle of ope
This seems to be a rather fruitful perennial on this mailing list. Do we have
a FAQ we can add this one to?
The general consensus seems to be: Before you ask about a memory leak in the
OpenSSL libraries, try doing your complete cycle of operations twice, and
seeing if you've "leaked" the same
> I'm suspecting a memory leak between RSA_new() and RSA_free().
I've forgotten: I'm using libssl0.9.7 :).
--
Marc Lasson.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Hello,
I'm a beginner in debugging programs and I apologyze myself:
- if this BUG is due to my poor skill and not to openSSL,
- if it's not good place to report BUGs,
- and for my english.
I'm suspecting a memory leak between RSA_new() and RSA_free().
[EMAIL PROTECTED]:~/bug$ cat bug.c
Openssl 0.98-dev provides system to implement additional ciphers and
message digest algorithms using dynamically loadable engines,
but doesn't seem to provide equivalent way for digital signature and
key distribution algorithms.
But there are much more digital signature algorithms then DSA and RS
