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
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.
- gnome-keyring-query — Provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.
- gkeyring — Query passwords from the command line. Unmaintained since November 2019.
- https://github.com/kparal/gkeyring || AUR, AUR
- gnome-keyring-query only requires libgnome-keyring as a build dependency.
- gkeyring requires libgnome-keyring as both a runtime and build dependency.
Manage using GUI
You can manage the contents of GNOME Keyring using Seahorse; install the package.
Passwords for keyrings (e.g., the default keyring, "Login") can be changed and even removed. In Seahorse, bring up the context menu for the keyring (e.g., Login) under Passwords and select Change Password. You will be prompted to enter the old password for this keyring. Upon doing so, you will be able to enter (and re-enter) a new keyring password. If you want to opt-out of using a password, simply leave both fields blank and select Continue. You will be warned about storing your passwords unencrypted; select Continue again to proceed.
Using the keyring outside GNOME
Without a display manager
If you are using automatic login, then you can disable the keyring manager by setting a blank password on the login keyring.
Start the gnome-keyring-daemon from
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
For SDDM, the file
/etc/pam.d/sddm already comes with the necessary changes.
Next, for GDM, add
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
- To use automatic unlocking, the same password for the user account and the keyring have to be set.
- You will still need the code in
~/.xinitrcbelow in order to export the environment variables required.
Start the gnome-keyring-daemon from xinitrc:
eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh) export SSH_AUTH_SOCK
See Xfce#SSH agents for use in Xfce.
With a display manager
When using a display manager, the keyring works out of the box for most cases. The following display managers automatically unlock the keyring once you log in:
One notable exception is SDDM in combination with the KDE Plasma desktop environment, which in its default configuration on many systems automatically unlocks KWallet but not the GNOME keyring. To fix this, edit
/etc/pam.d/sddm and add
auth optional pam_gnome_keyring.so
to the very end of the
auth section and
session optional pam_gnome_keyring.so auto_start
to the end of the
Should the same issue arise with another display manager, it can be fixed by doing the above in the corresponding file under
For GDM, the keyring's file name must be login.keyring to be automatically unlocked. GNOME will automatically create this keyring upon login.
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. See https://reddit.com/r/Fedora/comments/jwnqq5/ for more details.
To enable the keyring for applications run through the terminal, such as SSH, add the following to your
~/.zshenv, or similar:
if [ -n "$DESKTOP_SESSION" ];then eval $(gnome-keyring-daemon --start) export SSH_AUTH_SOCK fi
if test -n "$DESKTOP_SESSION" set -x (gnome-keyring-daemon --start | string split "=") end
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
Start SSH and Secrets components of keyring daemon
If you are starting GNOME Keyring with a display manager or the PAM method described in #PAM method and you are not using GNOME, Unity, Mate, or Cinnamon as your desktop environment, you may find that the SSH agent and Secret Service components are not started automatically. You can fix this by copying the
gnome-keyring-secrets.desktop files from
~/.config/autostart/ and by deleting the
OnlyShowIn=GNOME;Unity;MATE;Cinnamon; lines from each 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.
SSH_AUTH_SOCKto point to gnome-keyring regardless if it is running or not. To prevent this, you need to set the environment variable GSM_SKIP_SSH_AGENT_WORKAROUND before gnome-shell is started. One way to do this is to add the following line to
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. libsecret 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.
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 create a default keyring using Seahorse (a.k.a. Passwords and Keys), first create a new item by pressing
Ctrl+n; select Password keyring from the menu that appears. You will be prompted to enter a keyring name and then a password. You can choose not to use a password as mentioned in #Manage using GUI. The new keyring can be set as default by bringing up its context menu and selecting Set as default.
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.