Bug 2569332

Summary: libcap: source signature does not verify with openpgpverify (SHA-1 key self-signatures)
Product: [Fedora] Fedora Reporter: Jakub Jelen <jjelen>
Component: libcapAssignee: Carlos Rodriguez-Fernandez <carlosrodrifernandez>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: carlosrodrifernandez, dominik, go-sig
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2569052    

Description Jakub Jelen 2026-11-10 08:58:51 UTC
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 libcap, 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 e0b09e4b0b95):

    %openpgpverify --keyring=29EE848AE2CCF3F4.asc --signature=libcap-2.78.tar.sign --data=-

    Signing key on 38A644698C69787344E954CE29EE848AE2CCF3F4 is not bound:
               No binding signature at time 2026-04-05T18:09:50Z
      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-04-05) is by the key 38A644698C69787344E954CE29EE848AE2CCF3F4 (RSA 4096 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.)