GNOME Keyring is "a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications."
installed on its own. should also be installed to grant other applications access to your keyrings. Although is deprecated (and superseded by libsecret), it may still be required by certain applications.is a member of the group is thus usually present on systems running GNOME. The package can otherwise be
The gnome-keyring-daemon is automatically started via a systemd user service upon logging in. It can also be started upon request via a socket.
Extra utilities related to GNOME Keyring include:
- secret-tool — Access the GNOME Keyring (and any other service implementing the DBus Secret Service API) from the command line.
- lssecret — List all secret items using libsecret (e.g. GNOME Keyring).
- gnome-keyring-query — Provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.
Manage using GUI
You can manage the contents of GNOME Keyring using Seahorse; install the package.
Using the keyring
The PAM module pam_gnome_keyring.so initialises GNOME Keyring partially, unlocking the default login keyring in the process. The gnome-keyring-daemon is automatically started with a systemd user service.
- To use automatic unlocking with automatic login, you can set a blank password for the default keyring. Note that the contents of the keyring are stored unencrypted in this case.
- Alternatively, if using GDM and LUKS, GDM can unlock your keyring if it matches your LUKS password. For this to work, you need to use the systemd init in your mkinitcpio.conf as well as the appropriate kernel parameters[broken link: invalid section]. See  for more details.
- Skipping the PAM step works, because the next step[broken link: invalid section] will initialise the daemon when one is not running already; however, the default keyring is not unlocked in this case. More details are available at .
When using a display manager, the keyring works out of the box for most cases. GDM, LightDM, LXDM, and SDDM already have the necessary PAM configuration. For a display manager that does not automatically unlock the keyring edit the appropriate file instead of
/etc/pam.d/login as mentioned below.
When using console-based login, edit
auth optional pam_gnome_keyring.so at the end of the
auth section and
session optional pam_gnome_keyring.so auto_start at the end of the
#%PAM-1.0 auth required pam_securetty.so auth requisite pam_nologin.so auth include system-local-login auth optional pam_gnome_keyring.so account include system-local-login session include system-local-login session optional pam_gnome_keyring.so auto_start
gnome-keyring-daemon with the ssh component will start an SSH agent and automatically load all the keys in
~/.ssh/ that have corresponding .pub files. There is no way to remove these keys from the agent.
To list all loaded keys:
$ ssh-add -L
When you connect to a server that uses a loaded key with a password, a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you log in. If you check this, you will not need to enter your passphrase again!
To permanently save the a passphrase in the keyring, use ssh-askpass from thepackage:
$ /usr/lib/seahorse/ssh-askpass my_key
To manually add an SSH key from another directory:
$ ssh-add ~/.private/id_rsa Enter passphrase for ~/.private/id_rsa:
~/.ssh/id_rsa.pubin the example). Also, make sure that the public key is the file name of the private key plus .pub (for example,
To disable all manually added keys:
$ ssh-add -D
Enable the keyring ssh component
The default systemd user service shipped with the keyring does not include the ssh component. ssh must be added to the
--components option of the
gnome-keyring-daemon command in the
ExecStart line of the unit file.
See Systemd#Editing provided units for how to edit the keyring's systemd unit file.
Disable keyring daemon components
If you wish to run an alternative SSH agent (e.g. ssh-agent or gpg-agent), you need to disable the
ssh component of GNOME Keyring. To do so in an account-local way, copy
~/.config/autostart/ and then append the line
Hidden=true to the copied file. Then log out.
Tips and tricks
Integration with applications
$ gnome-keyring-daemon -r -d
This command starts gnome-keyring-daemon, shutting down previously running instances.
The GNOME keyring is useful in conjunction with Git when you are pushing over HTTPS. The package needs to be installed for this functionality to be available.
Configure Git to use the libsecret helper:
$ git config --global credential.helper /usr/lib/git-core/git-credential-libsecret
The next time you run
git push, you will be asked to unlock your keyring if it is not already unlocked.
Several applications which use GnuPG require a
pinentry-program to be set. Set the following to use GNOME 3 pinentry for GNOME Keyring to manage passphrase prompts.
Another option is to force loopback for GPG which should allow the passphrase to be entered in the application.
Renaming a keyring
The display name for a keyring (i.e., the name that appears in Seahorse and from
file) can be changed by changing the value of display-name in the unencrypted keyring file. Keyrings will usually be stored in
~/.local/share/keyrings/ with the .keyring file extension.
Automatically change keyring password with user password
password optional pam_gnome_keyring.so to the end of
#%PAM-1.0 #password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3 #password required pam_unix.so sha512 shadow use_authtok password required pam_unix.so sha512 shadow nullok password optional pam_gnome_keyring.so
Launching gnome-keyring-daemon outside desktop environments (KDE, GNOME, XFCE, ...)
If you are using sway, i3, or any window manager that does not execute
your window manager needs to execute the following commands during window manager startup. The commands do not need to be executed in any specific order.
dbus-update-activation-environment DISPLAY XAUTHORITY WAYLAND_DISPLAY
This command passes environment variables from the window manager to session dbus. Without this, GUI prompts cannot be triggered over DBus. For example, this is required for seahorse password prompt.
This is required because session dbus is started before graphical environment is started. Thus, session dbus does not know about the graphical environment you are in. Someone or something has to teach session dbus about the graphical environment by passing environment variables describing the graphical environment to session dbus.
gnome-keyring-daemon --start --components=secrets
During login, PAM starts
gnome-keyring-daemon --login which is responsible for keeping gnome-keyring unlocked with login password. If
gnome-keyring-daemon --login is not connected to session dbus within a few minutes,
gnome-keyring-daemon --login dies. If
gnome-keyring-daemon --start ... is started against session dbus in a window manager,
gnome-keyring-daemon --login is connected to session dbus. If your login session does not start
gnome-keyring-daemon --start ... before
gnome-keyring-daemon --login quits, you can also use any program that uses gnome-keyring or secret service API before
gnome-keyring-daemon --login dies.
Passwords are not remembered
If you are prompted for a password after logging in and you find that your passwords are not saved, then you may need to create/set a default keyring. To do this using Seahorse (a.k.a. Passwords and Keys), see Create a new keyring and Change the default keyring in GNOME Help.
Resetting the keyring
You will need to change your login keyring password if you receive the following error message: "The password you use to login to your computer no longer matches that of your login keyring".
Alternatively, you can remove the
user.keystore files from
~/.local/share/keyrings/. Be warned that this will permanently delete all saved keys. After removing the files, simply log out and log in again.
Unable to locate daemon control file
The following error may appear in the journal after logging in:
gkr-pam: unable to locate daemon control file
This message "can be safely ignored" if there are no other related issues .
No such secret collection at path: /
If you use a custom
~/.xinitrc and receive this error when trying to create a new keyring with Seahorse, this may be solved by adding the following line 
Terminal gives the message "discover_other_daemon: 1"
This is caused by gnome-keyring-deamon being started for the second time. Since a systemd service is delivered together with the daemon, you do not need to start it another way. So make sure to remove the start command from your
config.fish or similar. Alternatively you can disable the
gnome-keyring-daemon.socket user units.