liblegacy.a does not work unless compiled with -static
Dr Paul Dale
paul.dale at oracle.com
Sat May 2 07:34:00 UTC 2020
I’ve been wondering if an option to build the legacy provider into libcrypto (like the null and default providers) is worthwhile.
Given this conservation, it seems it might be.
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations
Phone +61 7 3031 7217
> On 2 May 2020, at 5:30 pm, Richard Levitte <levitte at openssl.org> wrote:
> On Fri, 01 May 2020 19:22:13 +0200,
> Salz, Rich via openssl-users wrote:
>> Hm, so DSO support is a requirement for legacy crypto now? That
>> probably needs to be made explicit, and see if the project gets
> No. When DSO support is turned off, the legacy provider code becomes
> part of libcrypto, in an inaccessible state (in other words, you still
> have to "load" it).
> Richard Levitte levitte at openssl.org
> OpenSSL Project http://www.openssl.org/~levitte/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openssl-users