[openssl-dev] [openssl.org #2325] memory corruption after libssl is unloaded from memory

This shouldn't be an issue any more with auto-init/auto-deinit in master. Closing this. Matt -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2325 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe:

[openssl.org #2325] memory corruption after libssl is unloaded from memory

hi, this has been shortly discussed on the OpenSSL dev list (sent on Aug 10, 2010). I understand that given the conditions needed to reproduce this error it will not be a priority but we believe it is a bug worth fixing so we would like to document it in the OpenSSL RT. Thank you.

Re: memory corruption after libssl is unloaded from memory

On Fri, 13 Aug 2010, Darryl Miles wrote: While it is possible to make a Valgrind clean (as in memory leaks) executable, that loads OpenSSL DSO/DLLs exactly once during the executable lifetime. I'm not sure it has ever been a feasible goal to make OpenSSL DSO/DLLs able to be unloaded (with

Re: memory corruption after libssl is unloaded from memory

On Fri, 13 Aug 2010, Ladar Levison wrote: I was able to dynamically load OpenSSL, initialize it, unload it, and then reload it back up again using your example along with some of my cleanup code. Since I don't know your specific use case, I don't know if something like this will work for you,

Re: memory corruption after libssl is unloaded from memory

On 8/16/2010 8:11 AM, Jan Pechanec wrote: On Fri, 13 Aug 2010, Ladar Levison wrote: I was able to dynamically load OpenSSL, initialize it, unload it, and then reload it back up again using your example along with some of my cleanup code. Since I don't know your specific use case, I don't know

Re: memory corruption after libssl is unloaded from memory

While it is possible to make a Valgrind clean (as in memory leaks) executable, that loads OpenSSL DSO/DLLs exactly once during the executable lifetime. I'm not sure it has ever been a feasible goal to make OpenSSL DSO/DLLs able to be unloaded (with the aim of subsequently loading). Let

Re: memory corruption after libssl is unloaded from memory

I was able to dynamically load OpenSSL, initialize it, unload it, and then reload it back up again using your example along with some of my cleanup code. Since I don't know your specific use case, I don't know if something like this will work for you, but figured I'd send it along just in

memory corruption after libssl is unloaded from memory

hi, when libssl is linked against modules that can be dlopen()ed and dlclose()d multiple times during the process life time, we hit a memory corruption where the hash table built in memory for the error strings references SSL strings in the address range previously occupied by libssl.