Sample
Disabling OpenSSL legacy provider via CRYPTOGRAPHY_OPENSSL_NO_LEGACY runtime environment variable causes legacy cipher operations to raise UnsupportedAlgorithm
sha256:98090b94729844a3359b8943ee2dcc5ea8569885ca1ce0bbe449f2bf38c2d002
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Disabling OpenSSL legacy provider via CRYPTOGRAPHY_OPENSSL_NO_LEGACY runtime environment variable causes legacy cipher operations to raise UnsupportedAlgorithm HOW
- Packages
- cryptography 47.0.0
- Environment
- python
- Created
- 2026-08-17T02:11:45Z
Commonly assumed
CRYPTOGRAPHY_OPENSSL_NO_LEGACY is a build-time compilation flag rather than a runtime environment variable evaluated when OpenSSL bindings initialize.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Setting CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1 before cryptography OpenSSL binding initialization prevents loading the OpenSSL legacy provider, causing Blowfish cipher encryptor creation to raise UnsupportedAlgorithm
- assert _rust.openssl._legacy_provider_loaded is False
- assert res.returncode == 0
Files
- NOTES.md
- csx.json
- requirements.lock
- requirements.txt
- test/contract.py
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- python 3.12 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9