Fedora Account System
Red Hat Associate
Red Hat Customer
As part of the Fedora 45 Change Sequoia openpgpverify (https://fedoraproject.org/wiki/Changes/Sequoia_openpgpverify), %gpgverify (GnuPG) is being replaced by %openpgpverify (Sequoia sqv). For libtpms, the switch can't be done in a simple PR: %gpgverify accepts the current upstream signature, but %openpgpverify rejects it. Failing check (dist-git commit ccc54eaed99d): %openpgpverify --keyring=gpgkey-B818B9CADF9089C2D5CEC66B75AD65802A0B4211.asc --signature=libtpms-0.10.2.tar.gz.asc --data=libtpms-0.10.2.tar.gz Signing key on B818B9CADF9089C2D5CEC66B75AD65802A0B4211 is not bound: No binding signature at time 2026-01-02T16:06:58Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure 0 of 1 signatures are valid (threshold is: 1). openpgpverify: Signature verification failed. Why: The release signature (SHA-512, made 2026-01-02) is by the key B818B9CADF9089C2D5CEC66B75AD65802A0B4211 (RSA 2048 bits). sqv reports only the first problem it hits (above). All the problems found: - The self-signatures that bind the key's user IDs to it use only SHA-1. SHA-1 is no longer considered secure: collisions have been practical since 2017 (SHAttered) and chosen-prefix collisions since 2020 (SHA-1 is a Shambles), and the crypto policy rejects it. GnuPG doesn't check self-signatures; Sequoia does, and without a valid one it doesn't use the key at all. The copy of the key on keys.openpgp.org, keyserver.ubuntu.com and WKD has the same problems. What can be done: - Ask upstream to refresh the key's self-signatures with SHA-256 and publish the updated key (keys.openpgp.org, WKD or the project website): gpg --cert-digest-algo SHA256 --quick-set-expire FPR 2030-12-31 gpg --cert-digest-algo SHA256 --quick-set-expire FPR 2030-12-31 '*' Use an absolute expiry date (or 0). Releases signed after this verify. - For the release already in Fedora, ask upstream to sign the same tarball again with the updated key and publish the new signature (the tarball doesn't change), or wait for the next release. Then update the keyring and the signature in dist-git. - If upstream already signs with a newer key, switch the keyring to that key. - Only if re-signing is not an option: the new self-signatures can be dated one second after the key (or its newest subkey) was created, so that the existing release signatures verify too. Backdating is unusual and easy to get wrong, so it is a last resort; Updating GPG keys for Fedora and RHEL (https://www.redhat.com/en/blog/updating-gpg-keys-for-fedora-and-rhel) describes how (gpg --faked-system-time "$((CT + 1))!" --cert-digest-algo SHA256 --quick-set-expire ..., with CT that creation time). The rest of the conversion is mechanical. Once the signature or key is sorted out, the spec change is the same as for other packages: %{gpgverify} → %{openpgpverify} and BuildRequires: openpgpverify. I'm happy to send the PR. (The check was run with scripts from https://github.com/Jakuje/openpgpverify-migration.)
I now sent my updated self-signature with the following command and updated the signature v0.10.2.tar.gz.asc on the libtpms v0.10.2 release: gpg --keyserver hkps://keys.openpgp.org --send-keys B818B9CADF9089C2D5CEC66B75AD65802A0B4211 How far does this get us now?
Hello, thank you for the prompt reply. With the updated key from keyserver and this signature, everything works just fine! Please, let me know if I should open a Fedora dist git PR for you, or you will take care of that. Given that the new signature file has the same name as the old one, I think the lookaside cache will not accept it so it will likely have to live in the dist git itself until the next release.
(In reply to Jakub Jelen from comment #2) > Hello, thank you for the prompt reply. With the updated key from keyserver > and this signature, everything works just fine! > > Please, let me know if I should open a Fedora dist git PR for you, or you > will take care of that. Given that the new signature file has the same name > as the old one, I think the lookaside cache will not accept it so it will > likely have to live in the dist git itself until the next release. Sure, please do. Thanks.