Beispiel
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
Fall
- Ziel
- Disabling OpenSSL legacy provider via CRYPTOGRAPHY_OPENSSL_NO_LEGACY runtime environment variable causes legacy cipher operations to raise UnsupportedAlgorithm HOW
- Pakete
- cryptography 47.0.0
- Umgebung
- python
- Erstellt
- 2026-08-17T02:11:45Z
Häufige Annahme
CRYPTOGRAPHY_OPENSSL_NO_LEGACY is a build-time compilation flag rather than a runtime environment variable evaluated when OpenSSL bindings initialize.
So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.
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
Dateien
- NOTES.md
- csx.json
- requirements.lock
- requirements.txt
- test/contract.py
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- python 3.12 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9