mNo edit summary |
mNo edit summary |
||
| Line 87: | Line 87: | ||
== Scope == | == Scope == | ||
* Proposal owners: gnome-keyring-daemon currently provides 3 services: D-Bus secret-service, ssh-agent wrapper, and a control socket for PAM to automatically unlock the login keyring. Those services are either split out, or removed in favor of other means, in the following steps: | * Proposal owners: gnome-keyring-daemon currently provides 3 services: D-Bus secret-service, ssh-agent wrapper, and a control socket for PAM to automatically unlock the login keyring. Those services are either split out, or removed in favor of other means, in the following steps: | ||
** | ** Make the D-Bus secret-service D-Bus activatable | ||
** | ** Make the ssh-agent wrapper code socket activatable | ||
** Modify the PAM module to use libsecret API to unlock the login keyring, instead of the control socket | ** Modify the PAM module to use libsecret API to unlock the login keyring, instead of the control socket | ||
** Install systemd unit files for those services, modify the current session initialization sequence to use them | ** Install systemd unit files for those services, modify the current session initialization sequence to use them | ||
** (Stretch goal) move the | ** (Stretch goal) move the service implementations from gnome-keyring to more appropriate packages (gcr and libsecret) and remove the gnome-keyring package from the default compose | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
Revision as of 09:05, 26 October 2020
Modular GNOME Keyring services
Summary
The monolithic daemon provided by GNOME Keyring will be split into dedicated sub-daemons, so that they can be consistently managed by systemd.
Owner
- Name: Daiki Ueno
- Email: dueno@redhat.com
- Name: Benjamin Berg
- Email: bberg@redhat.com
- Product: Workstation
- Responsible WG: Workstation
Current status
- Targeted release: Fedora 34
- Last updated: 2020-10-26
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
GNOME Keyring was originally designed to be the central cryptographic service on desktop, though its scope has been gradually reduced over years. Notable examples are gpg-agent removal in 2015, PKCS #11 module deprecation and ssh-agent rewrite to wrap ssh-agent from OpenSSH in 2018.
All the GNOME Keyring services are exposed as part of a single daemon program called gnome-keyring-daemon, launched by the session manager (gnome-session) or PAM, depending on desktop environments. Now that only the essential service remaining in gnome-keyring-daemon are D-Bus secret-service and the ssh-agent wrapper, it would be worth splitting the daemon into sub-daemons, so they can be managed by systemd.
Feedback
Benefit to Fedora
This will bring in consistent experience of setting up and managing the GNOME Keyring services, taking advantage of the fine grained systemd service units. This would simplify the security related services running on desktop, and make it easier to adopt modern security features e.g., hardware-based security.
Scope
- Proposal owners: gnome-keyring-daemon currently provides 3 services: D-Bus secret-service, ssh-agent wrapper, and a control socket for PAM to automatically unlock the login keyring. Those services are either split out, or removed in favor of other means, in the following steps:
- Make the D-Bus secret-service D-Bus activatable
- Make the ssh-agent wrapper code socket activatable
- Modify the PAM module to use libsecret API to unlock the login keyring, instead of the control socket
- Install systemd unit files for those services, modify the current session initialization sequence to use them
- (Stretch goal) move the service implementations from gnome-keyring to more appropriate packages (gcr and libsecret) and remove the gnome-keyring package from the default compose
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
The migration should be transparent.
N/A (not a System Wide Change)
How To Test
Check if the GNOME Keyring services are now managed by systemd, using systemctl status. Check if the existing applications (Seahorse, SSH clients, etc.) still work.
N/A (not a System Wide Change)
User Experience
No visible change should be observed by normal users.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)