The python-cryptography rpms
Find a file
Jeremy Cline 96d09f3c86
Update to v48.0.0
Full changelog: https://cryptography.io/en/latest/changelog/#v48-0-0

This contains one backwards-incompatible change, but which is in a
failure path where the previous behavior was unexpected.

 - BACKWARDS INCOMPATIBLE: Loading an X.509 CRL whose inner
   TBSCertList.signature algorithm does not match the outer
   signatureAlgorithm now raises ValueError. Previously, such CRLs were
   parsed successfully and only rejected during signature validation.

 - Added support for ML-KEM key encapsulation and ML-DSA signing when
   using OpenSSL 3.5.0 or later

Signed-off-by: Jeremy Cline <jeremycline@microsoft.com>
2026-05-05 07:49:03 -04:00
.gitignore Update to v48.0.0 2026-05-05 07:49:03 -04:00
0001-Lower-cc-dependency.patch Update to v48.0.0 2026-05-05 07:49:03 -04:00
changelog Switch to autorelease and autochangelog macros 2024-07-03 10:27:54 -04:00
conftest-skipper.py Skip iso8601 and pretend tests on RHEL 2021-02-12 16:47:08 +01:00
python-cryptography.spec Update to v48.0.0 2026-05-05 07:49:03 -04:00
README.md Update to 3.4.7, use vectors from sources (#1952024) 2021-04-22 08:07:57 +02:00
sources Update to v48.0.0 2026-05-05 07:49:03 -04:00
vendor_rust.py Update to 42.0.8, resolves RHBZ#2251816" 2024-07-03 09:25:42 -04:00

PyCA cryptography

https://cryptography.io/en/latest/

Packaging python-cryptography

The example assumes

  • Fedora Rawhide (f34)
  • PyCA cryptography release 3.4
  • Update Bugzilla issue is RHBZ#00000001

Build new python-cryptography

Switch and update branch

fedpkg switch-branch rawhide
fedpkg pull

Bump version and get sources

rpmdev-bumpspec -c "Update to 3.4 (#00000001)" -n 3.4 python-cryptography.spec
spectool -gf python-cryptography.spec

Upload new source

fedpkg new-sources cryptography-3.4.tar.gz

Commit changes

fedpkg commit --clog
fedpkg push

Build

fedpkg build

RHEL/CentOS builds

RHEL and CentOS use a different approach for Rust crates packaging than Fedora. On Fedora Rust dependencies are packaged as RPMs, e.g. rust-pyo3+default-devel RPM. These packages don't exist on RHEL and CentOS. Instead python-cryptography uses a tar ball with vendored crates. The tar ball is created by a script:

./vendor_rust.py
rhpkg upload cryptography-3.4-vendor.tar.bz2