[openssl-users] Openssl static build linked in DLL does not unload on win32
Michael.Wojcik at microfocus.com
Fri Jan 6 16:37:28 UTC 2017
> Can you not link against the OpenSSL DLLs rather than statically link?
> That would avoid the problem.
It introduces other problems. It means either shipping the OpenSSL DLLs or requiring the customer provide them; the former can have legal implications (cryptographic export licensing, for example), while the latter is a usability issue. It means the calling library no longer controls what version of OpenSSL is used, since the DLLs can be replaced.
I haven't looked at the 1.1.x source to see what OPENSSL_cleanup is doing, but it certainly sounds like a bad idea. What kind of cleanup needs to happen at process exit (in the typical environment in which OpenSSL is used)? I suppose I'll have to take a look at the source, but I'd be very interested to hear the rationale.
Distinguished Engineer, Micro Focus
More information about the openssl-users