fesco/tickets
13
2
Fork 1
Code Issues 19 Pull requests Activity

Change: Sequoia openpgpverify #3660

New issue
Closed
opened 2026-07-28 15:29:38 +00:00 by amoloney · 6 comments
amoloney commented 2026-07-28 15:29:38 +00:00
Owner
Copy link

Introduce a rpm macro %openpgpverify and update packages to use it instead of existing gnupg specific %gpgverify. The new macro will use a standard OpenPGP implementation from Sequoia instead of GnuPG by default to provide support for Post Quantum Cryptography as defined in the OpenPGP WG. This is part of a gradual switching from GnuPG as dependency.

Owners, do not implement this work until the FESCo vote has explicitly ended.
When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the FESCo ticket policy and the Changes policy for more information.
If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.

Introduce a rpm macro %openpgpverify and update packages to use it instead of existing gnupg specific %gpgverify. The new macro will use a standard OpenPGP implementation from Sequoia instead of GnuPG by default to provide support for Post Quantum Cryptography as defined in the OpenPGP WG. This is part of a gradual switching from GnuPG as dependency. * [Change proposal](https://fedoraproject.org/wiki/Changes/Sequoia_openpgpverify) * [devel post](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/AX64EE3PMT2IRGK2YJUJ37MADHNUGVMS/) * [Discourse discussion](https://discussion.fedoraproject.org/t/f45-change-proposal-sequoia-opengpgverify-self-contained/197231) * Owners: @jjelen @decathorpe **Owners, do not implement this work until the FESCo vote has explicitly ended.** When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the [FESCo ticket policy](https://docs.fedoraproject.org/en-US/fesco/#_ticket_policy) and the [Changes policy](https://docs.fedoraproject.org/en-US/program_management/changes_policy/) for more information. If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update. **REMINDER**: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the [Fedora Devel](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/) mailing list.
amoloney commented 2026-07-28 15:30:36 +00:00
Author
Owner
Copy link

@jjelen @decathorpe tagging in a comment under this issue should give you a notification of this ticket for your change proposals submission to FESCo.

@jjelen @decathorpe tagging in a comment under this issue should give you a notification of this ticket for your change proposals submission to FESCo.
👀 1
gotmax23 commented 2026-07-28 15:57:38 +00:00
Owner
Copy link

+1

+1
kevin commented 2026-07-30 19:19:23 +00:00
Owner
Copy link

+1

+1
zbyszek commented 2026-07-30 21:08:11 +00:00
Owner
Copy link

I'm still not entirely sold on the change of the macro name, but if the change owners like this approach the best, so be it.

+1

I'm still not entirely sold on the change of the macro name, but if the change owners like this approach the best, so be it. +1
siosm commented 2026-07-31 15:02:02 +00:00
Owner
Copy link

+1

+1
decathorpe commented 2026-08-04 18:22:10 +00:00
Owner
Copy link

This is APPROVED after 7 days (+4, 0, -0).

This is APPROVED after 7 days (+4, 0, -0).
gotmax23 2026-08-10 18:50:00 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
document it
A new policy/recommendation needs to be documented

  
fast track
A swift resolution is critical, +7,-0 immediately approves the ticket

  
meeting
This ticket will be on the meting agenda

  
next release
The Change was postponed to next release

  
nonresponsive maintainer
Tickets about nonresponsive maintainers

  
packager revocation
Tickets about revoking packager privileges

  
pending announcement
Approved/rejected tickets to be announced alongside the next meeting agenda

  
provenpackager
A request to become a provenpackager

  
python 2 exception
An exception request to continue to use Python 2 in Fedora 32+

  
self contained change
Tickets with Self Contained Change proposals

  
stalled
Tickets that are stalled, FESCo won't regularly triage them

  
Status
Accepted
 Ticket contains a proposal that was accepted

  
Status
Duplicate
 Ticket rejected for being a duplicate

  
Status
Insufficient data
 Ticket rejected due to insufficient information being available

  
Status
Invalid
 Ticket rejected due to being invalid or misfiled

  
Status
Rejected
 Ticket contains a proposal that was rejected

  
system wide change
Tickets with System Wide Change proposals

  
updates policy exception
Tickets for exceptions from the Updates Policy

  
vote-in-progress
Vote is currently in progress in the ticket

No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
Milestone
Clear milestone
No items
No milestone
Fedora Linux 45
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fesco/tickets#3660
No description provided.