fix: set CRYPTOGRAPHY_OPENSSL_NO_LEGACY #4784
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cryptography>=42.0 cannot load legacy algorithms on Ubuntu 20.04 for armhf, ppc64el, riscv64, and s390x See https://cryptography.io/en/latest/openssl/#legacy-provider-in-openssl-3-x Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com>
cmatsuoka
approved these changes
May 2, 2024
lengau
approved these changes
May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tox run -m lint?tox run -e test-py310? (supported versions:py39,py310,py311,py312)cryptography>=42.0 cannot load legacy algorithms on Ubuntu 20.04 for armhf, ppc64el, riscv64, and s390x.
@cmatsuoka was able to verify this fix in an emulated riscv64 20.04 machine from here.
See https://cryptography.io/en/latest/openssl/#legacy-provider-in-openssl-3-x for details on legacy algorithms.
Fixes LP#2064639