cryptography
cryptography copied to clipboard
pyca
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
Bumps [readme-renderer](https://github.com/pypa/readme_renderer) from 43.0 to 44.0. Release notes Sourced from readme-renderer's releases. 44.0 What's Changed Support newer docutils versions by @kurtmckee in pypa/readme_renderer#315 Resolve Node 16 deprecation warnings in CI...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Closes #11195 - [x] Added OID for `PRIVATE_KEY_USAGE_PERIOD` - [x] Added `PrivateKeyUsagePeriod` under `/x509/extensions.py` - [ ] Added test to increase coverage
[RSA Full Domain Hash](https://en.wikipedia.org/wiki/Full_Domain_Hash) is secure and can be used in combination with XOFs such as SHAKE. PKCS#1 1.5 without ASN.1 prefix, aka [LTC_PKCS_1_V1_5_NA1](https://github.com/libtom/libtomcrypt/blob/7e7eb695d581782f04b24dc444cbfde86af59853/src/headers/tomcrypt_pkcs.h#L26), is a padding scheme that only...
Fedora 41 and RHEL 10 are deprecating and phasing out OpenSSL ENGINE support. Downstream has moved `openssl/engine.h` into a separate RPM package and is recompiling packages with `-DOPENSSL_NO_ENGINE=1`. The compiler...
On a system without openssl engine, such as CentOS Stream 10, I cannot compile cryptography with `-DOPENSSL_NO_ENGINE=1`. * Versions of Python, ``cryptography``, ``cffi``, ``pip``, and ``setuptools`` you're using * Python...
* Versions of Python, ``cryptography``, ``cffi``, ``pip``, and ``setuptools`` you're using I'm working on a Linux machine with: ``` Package Version ------------- ------- cffi 1.16.0 cryptography 42.0.8 pip 24.1.1 setuptools...
There was previous discussion in #8148 regarding a Windows on ARM wheel. That was closed with these comments: > We won't ship a wheel for a platform we can't test...
Another quick preliminary PR that just refactors some existing code to make implementation of user-provided extension policies more straightforward. (A good change even on it's own in my opinion.)
Finally coming back with another PR. The idea is that this one will serve to confirm the user-facing API for custom extension policy support, and the next one will have...