You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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).
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?
The text was updated successfully, but these errors were encountered: