示例
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
案例
- 目标
- Disabling OpenSSL legacy provider via CRYPTOGRAPHY_OPENSSL_NO_LEGACY runtime environment variable causes legacy cipher operations to raise UnsupportedAlgorithm HOW
- 包
- cryptography 47.0.0
- 环境
- python
- 创建时间
- 2026-08-17T02:11:45Z
常见的想当然
CRYPTOGRAPHY_OPENSSL_NO_LEGACY is a build-time compilation flag rather than a runtime environment variable evaluated when OpenSSL bindings initialize.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- 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
文件
- NOTES.md
- csx.json
- requirements.lock
- requirements.txt
- test/contract.py
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- python 3.12 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9