freenode
Distributions & Plumbing

Fedora proposes hybrid post-quantum signatures for releases

The Fedora 48 change would replace RSA-4096 OpenPGP signing; older RHEL largely ignores the new signatures rather than rejecting packages.

Fedora is proposing to stop signing release artifacts with RSA-4096 OpenPGP keys and switch to a hybrid of ML-DSA-87 and Ed448. The change, aimed at Fedora Linux 48, still needs approval from the Fedora Engineering Steering Committee.

The proposal, owned by Jeremy Cline, covers signatures on RPMs, installation images, and other release artifacts. A cryptographically relevant quantum computer running Shor's algorithm could forge RSA signatures of the size Fedora uses today. NIST standardized ML-DSA for quantum-resistant signatures in 2024, and RFC 9980 added those algorithms to OpenPGP. Under the hybrid scheme, both an ML-DSA-87 signature and an Ed448 signature must be valid, so a later flaw in the newer algorithm would not by itself make a Fedora signature acceptable.

The practical question is what older systems do with signatures they cannot understand. Clemens Lang, of Red Hat's RHEL crypto team, wrote that RHEL 10.1 and later, and RHEL 9.7 and later, can handle RPM 6.0 and post-quantum OpenPGP v6 signatures, and will either verify or ignore them depending on configuration. Testing down to RHEL 9.0 showed those systems gracefully ignore the signatures, so the packages still work. He initially warned that RHEL 8 might fail to parse them because the signature is larger than older RPM header limits allow.

Panu Matilainen corrected that point: RHEL 8 should still ignore the signatures rather than reject the package, because those size limits were already raised upstream for IMA signatures. RHEL 7 and older can hit the limit, but that line was already crossed by IMA file signatures in both Fedora and RHEL.

The proposal says the needed tooling, except ostree, is available from Fedora 43, and that Enterprise Linux 10.1 and later should be supported. GnuPG on systems that lack a new enough copy of rpm-sequoia still cannot validate these signatures, even though upstream GnuPG is adding ML-DSA support following RFC 9980.