Change: oo7 Secrets Service Provider #3640

Closed
opened 2026-07-14 11:17:50 +00:00 by amoloney · 5 comments
Owner

Switch the default Secrets Service provider for Fedora desktops from KWallet and GNOME Keyring to oo7.

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.

Switch the default Secrets Service provider for Fedora desktops from KWallet and GNOME Keyring to oo7. * [Change proposal](https://fedoraproject.org/wiki/Changes/oo7_Secrets_Service_Provider) * [devel post](https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/MFGKLUQVOSQYZE6TT65JBSKWESFYYCR5/) * [Discourse discussion](https://discussion.fedoraproject.org/t/f45-change-proposal-oo7-secrets-service-provider-system-wide/195274) * Owners: @ngompa @decathorpe @salimma **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.
Owner

+1

+1
Owner

+1

+1
Owner

+1

Based on the discussion in the various trackers linked from the mailing list discussion, there might be some integration problems with the myriad tools that access the keyring. But the best way to figure those out is to prepare the new daemon and all the needed integration in Fedora, and then ask volunteers to switch over, and then if things generally work, flip the default. So we need to keep an eye and be ready to invoke the contingency plan if there are too many problems.

+1 Based on the discussion in the various trackers linked from the mailing list discussion, there might be some integration problems with the myriad tools that access the keyring. But the best way to figure those out is to prepare the new daemon and all the needed integration in Fedora, and then ask volunteers to switch over, and then if things generally work, flip the default. So we need to keep an eye and be ready to invoke the contingency plan if there are too many problems.
Owner

+1 agree with @zbyszek.

+1 agree with @zbyszek.
Owner

After a week: APPROVED (+4, 0, 0)

I'll include the announcement in today's agenda.

After a week: APPROVED (+4, 0, 0) I'll include the announcement in today's agenda.
zbyszek 2026-07-21 11:57:38 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
5 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#3640
No description provided.