[openssl-users] Initialising OpenSSL more than once - how do we handle this?

[Jakob Bohm]

On 31/07/2018 01:10, Jordan Brown wrote:
> On 7/30/2018 12:27 PM, Viktor Dukhovni wrote:
>> The only time such "leaks" come into play is process exit and library 
>> unload.
>
> Process exit is not the only time that libraries get unloaded.  I 
> don't happen to remember any details, but I know we've had problems 
> with libraries that got unloaded because they were dependencies of 
> other shared objects that are intended to be used on a "load, call, 
> unload" basis.
>
And *this* is the reason why having a common library like OpenSSL
or libc refuse to get unloaded on the fly is such a horrible idea.
I still recall the problems when (decades ago) Borland added such
anti-unload code to some of their compiler-bundled libraries.

There are processes that naturally run for a lot longer than the
library-format plugins inside them, and it is highly valuable to
end users to be able to upgrade those plugins on the fly without
restarting the long-lived container, with all the other state it
holds.

Enjoy

Jakob
-- 
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded