OpenSSL version 3.0.0-alpha1 published

[Nicola Tuveri]

At https://wiki.openssl.org/index.php/OpenSSL_3.0#Providers there was
already an example of how to do this programmatically, and a link to the
manpage for the config file syntax.

I just added also a minimal config file example to load both the default
and the legacy provider in the default library context.


Cheers,

Nicola

On Fri, 24 Apr 2020 at 17:56, Sam Roberts <vieuxtech at gmail.com> wrote:

> On Fri, Apr 24, 2020 at 1:05 AM Matt Caswell <matt at openssl.org> wrote:
> > This one is interesting:
> >
> > ERR_OSSL_EVP_FETCH_FAILED
> >
> >
> > This means that the algorithm you are trying to use isn't available in
> > the loaded providers. Since you should be getting the default provider
> > loaded automatically it could be because some legacy algorithms were
> > moved to the legacy provider (MD2, MD4, MDC2, RMD160, CAST5, BF
> > (Blowfish), IDEA, SEED, RC2, RC4, RC5 and DES (but not 3DES)). If you're
> > using something from that list then that would explain it.
>
> Can we add the legacy provider, via configuration, or via code?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20200424/069dd245/attachment.html>