On 02/05/2020 16:39, Sam Roberts wrote:
> On Sat, May 2, 2020 at 12:31 AM Richard Levitte wrote:
>> 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).
>
> Using OSSL_PROVIDER_loa
On Sat, May 2, 2020 at 12:31 AM Richard Levitte wrote:
> 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).
Using OSSL_PROVIDER_load(NULL, "legacy")?
My first try after a static only
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.
Pauli
--
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations
Phone +61 7 3031 7217
Oracle Australia
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
> pushback.
No. When DSO support is turned off, the legacy provider code becomes
part of
On Fri, May 1, 2020 at 10:22 AM 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 pushback.
It would mean legacy alg support would not exist for Node.js binary
distributions, bu
Hm, so DSO support is a requirement for legacy crypto now? That probably needs
to be made explicit, and see if the project gets pushback.
OK I see, thanks.
On Fri, May 1, 2020 at 6:27 PM Matt Caswell wrote:
> liblegacy.a is an internal artifact! You're not supposed to link your
> applications against it!
>
> You are supposed to link against libcrypto normally. If legacy.so isn't
> in the default install location then make sure the
liblegacy.a is an internal artifact! You're not supposed to link your
applications against it!
You are supposed to link against libcrypto normally. If legacy.so isn't
in the default install location then make sure the OPENSSL_MODULES
environment variable is pointing at its directory.
Matt
On 01
When I configure using "./config enable-legacy" it creates
providers/liblegacy.a, then in the program I link with it,
OSSL_PROVIDER_load fails (returns NULL).
When I configure using "./config enable-legacy -static" it works as
expected.
However, building with -static fails on OSS-Fuzz when buildi
