After a decade of silence, time to face facts that global library cleanup isn't
a high priority, and does have
some concerns/drawbacks (see Pete's note in the RT). We're nog going to address
this unless someone
on the team, or someone with a patch, re-opens the ticket.
--
Rich Salz, OpenSSL dev tea
On Wed, Dec 03, 2003 at 08:50:49AM +0100, [EMAIL PROTECTED] via RT wrote:
> But it never went any further than that, ie. a discussion. Please feel
> free to open an RT ticket about this and assign ownership to me if you
> like so that it doesn't slip through the cracks...
It was my pleasure...
Hi there,
On December 2, 2003 06:29 pm, Verdon Walker wrote:
> Should OpenSSL formalize a mechanism for cleaning up global library
> resources? Or is it sufficient to let the OS do that work?
I've got way too much on my plate right now to do anything more than make
a passing comment, but that w
Potentially useful, but ...
A problem we frequently hit is multiple instances of libraries in a single
process - often due to applications dragging in shared library
dependencies they aren't explicitly aware of.
For that reason, this is only "mostly safe" if you can reference count
somehow, o
Although OpenSSL has an initialization routine (SSL_library_init), it
does not have a corresponding cleanup routine (SSL_library_cleanup). It
does have a few cleanup routines (e.g. EVP_cleanup, OBJ_cleanup, etc.)
but no overall cleanup function.
This has been an issue for us when running OpenSSL