Bug 2569052 (openpgpverify-migration) - Tracker for packages using incompatible keys for tarball verification
Summary: Tracker for packages using incompatible keys for tarball verification
Keywords:
Status: NEW
Alias: openpgpverify-migration
Product: Fedora
Classification: Fedora
Component: distribution
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aoife Moloney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2569053 2569054 2569055 2569056 2569057 2569058 2569321 2569322 2569323 2569324 2569325 2569326 2569327 2569328 2569329 2569330 2569331 2569332 2569333 2569334 2569335 2569336 2569337 2569338 2569339 2569340 2569341 2569342 2569343 2569344 2571537 2571538 2571539 2571540 2571541 2571542 2571543 2571544 2571545 2571546 2571547 2571552 2571562 2571567 2571568 2571569 2571571 2571572 2571573 2571574 2571575 2571576 2571577 2571578 2571579 2571580 2571581 2571582 2571583 2571586 2571587 2571588 2571589 2571590 2571591 2571592 2571593 2571594 2571595 2571596 2572238 2572239 2572240 2572242 2572243 2572244 2572245 2572246 2572248 2572249 2572250 2572251 2572252 2572253 2572254 2572255 2572256 2572257 2572258 2572259 2572260 2572261 2572263 2572264 2572267 2572268 2572269 2572270 2572271 2572272 2572273 2572274 2572280 2572282 2572283 2572284 2572285 2572287 2572288 2572289 2572290 2572291 2523619 2572241 2572265 2572266 2572286
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-09 10:57 UTC by Jakub Jelen
Modified: 2026-11-12 08:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jakub Jelen 2026-11-09 10:57:59 UTC
This is a tracking bug for changes following up to the Fedora Change "Sequoia %openpgpverify":
https://fedoraproject.org/wiki/Changes/Sequoia_openpgpverify (bug 2523619)

The Change added %openpgpverify, which verifies upstream source signatures with Sequoia sqv instead of GnuPG. Packages that use %gpgverify or call gpg directly are being moved to it. For most of them a small spec change is enough, and those get pull requests in dist-git.

The bugs blocking this tracker are for packages where that is not enough: GnuPG accepts the upstream signature, but sqv rejects it. The signing key or the signature uses cryptography that the system crypto policy no longer accepts, or the keyring in dist-git is outdated. GnuPG doesn't check most of this; sqv does. Fixing it needs upstream or the maintainer, so each package gets its own bug with the failing check, every problem found, and what can be done. Until it is fixed, the package keeps %gpgverify.

We plan to open about 116 bugs (29 of them for packages in the ELN buildroot), in these groups:

- Key algorithm rejected (DSA, or RSA shorter than 2048 bits): about 48 packages. Upstream needs a new key.
- Key self-signatures use only SHA-1: about 48 packages. Upstream refreshes the key's self-signatures with SHA-256 and re-signs the current release, or the next release verifies.
- Release signature made with SHA-1: about 9 packages, 8 of them with SHA-1 self-signatures as well. Upstream signs with SHA-256 (and refreshes the key).
- Key expired before the release was signed: about 8 packages. Upstream publishes the extended key, or re-signs.
- Other keyring problems: 3 packages (a version 3 key in the keyring, or a keyring without the older self-signatures).

The bugs are filed in small batches, starting with a pilot of 6. The checks, the per-package details and the bug texts are at:
https://github.com/Jakuje/openpgpverify-migration (see reports/bugs-2026-11-09.md)


Note You need to log in before you can comment on or make changes to this bug.