[openssl] Static builds should maybe set no-module
configure option
#24559
Labels
category:port-feature
The issue is with a library, which is requesting new capabilities that didn’t exist
Is your feature request related to a problem? Please describe.
OpenSSL 3.0 deprecated some old algorithms like RC2-40-CBC, which are still in use in some PKCS#12 certificates. Using them requires something like
at the start of your program; however, a static OpenSSL build (
no-shared
) will try to dynamically load e.g. legacy.so, which will not exist. To make the legacy provider available in static builds, OpenSSL needs to be built withno-shared no-module
(see openssl/openssl#17679).Proposed solution
OpenSSL (at least on Unix? Not sure about other platforms) should probably have https://github.com/microsoft/vcpkg/blob/master/ports/openssl/unix/CMakeLists.txt#L130 be
set(SHARED no-shared no-module)
Describe alternatives you've considered
I don't know if there is a use-case for dynamically loading these modules for a static build?
The text was updated successfully, but these errors were encountered: