Remove no longer needed CRYPTOGRAPHY_ALLOW_OPENSSL_102 environment variable #6606
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.
SecureDrop has dropped support of Xenial in #5725
As described in the
cryptography
documentation, theCRYPTOGRAPHY_ALLOW_OPENSSL_102
was used to force compatibility betweencryptography==3.2
and OpenSSL 1.0.2.The current version of OpenSSL in Focal is in the 1.1 branch and also
cryptography
is now pinned to thecryptography>=3.4.7
version.The description of the original compatibility issue is here https://cryptography.io/en/3.2/faq/
The commit of the original change is here 4569657
Status
Ready for review
Description of Changes
Dropping the flag should have no effect on any supported system.
Testing
A normal test run in staging and prod, if any function that uses the cryptography module works, then everything should be working as usual.
Checklist
My staging environment is currently undergoing other disruptive testing and thus I have not run the infra tests yet.
Configuration tests pass
These changes do not require documentation