Legacy Provider support?

[wyllys66]

I have an app that requires access to one of the old deprecated ciphers - CAST5. According to OpenSSL, I should be able to load the "legacy" provider to get access to these older algs, but when I try it fails.

Is "legacy" provider support a configurable option that can be made available?

[wyllys66]

I figured out that the legacy providers can be included in libcrypto.a if you use the "no-module" option to the "Configure" script when building. Can this be added to the baseline in a future release? Older code supporting things like PGP need access to some of the legacy crypto (CAST5 in particular).

[dbrkic-proglove]

Any updates on this?

[jdanthinne]

I guess using an OpenSSL 1.x version could resolve this, but no release was signed, unfortunately… see #201.

[krzyzanowskim]

Just released 1.1.2300

[peterferguson]

@krzyzanowskim could you also release 1.1.2300 on cocoapods 🙏

having a build issue due to bitcode and afaict this is the only v1 version without bitcode

[krzyzanowskim]

could you also release 1.1.2300 on cocoapods

done 1.1.2301

[rafcabezas]

Thank you so much for this ❤️. Would you be able to also provide this signed 1.1.2300 in OpenSSL-Package 🙏