Is there a way to automatically unlock the GNOME Keyring?

Is there a way to automatically unlock the GNOME Keyring?

I’ve tried the PAM method to automatically unlock the keyring as described here and here but it does not work because (I think) I’m not using the keyring ‘outside’ Gnome.

Why is the GNOME Keyring locked in Seahorse?

But applications sill can’t access it and seahorse shows no entry. and rerun the start commanid, it works, although the keyrings are still locked which makes sense… (it’s how I’ve been doing until now to connect to wifi and post here ) Thanks again!

Why does Deja DUP not unlock the SSH key?

First few boots it worked fine, but now the login keyring isn’t getting unlocked automatically. It is also interesting that if Déjà Dup fails even one time because it can’t unlock the ssh key, it will fail any next backups, since it thinks that the directory it backs up to is the backup directory of an another computer.

How to unlock the keyring when login in from the console?

Then log in and check if gnome-keyring-daemon is running to see if PAM has started it. Then run that “gnome-keyring-daemon –start” command yourself manually and see what happens. The entries in /run/user/1000/keyring/ are not normal files. They are “sockets”.

Gnome Keyring: Automatic Unlocking / PAM Gnome keyring can automatically unlock the ‘login’ keyring when the user logs in. Other keyrings or key storage may have their unlock passwords stored in the ‘login’ keyring, and are then automatically unlocked when necessary. This is usually installed by default by a distro or OS distributor.

How does the PAM module unlock the keyring?

Upon authenticating the user, the PAM module tries to unlock the ‘login’ keyring with the password entered by the user. If the ‘login’ keyring does not exist it is created with the user’s password. If the ‘login’ is the first and only keyring it will become the default keyring.

What does Pam do if GNOME Keyring is not running?

Upon authenticating the user, or logging into the session, the PAM module checks for the GNOME_KEYRING_CONTROL environment variable. If not present it assumes that gnome-keyring-daemon is not running for that session. If the auto_start argument is present in the PAM config, it then starts it as a daemon.

How does the PAM module work in GDM?

For example, auto_start only_if=gdm,xdm will only start the daemon if the process is gdm or xdm. Upon authenticating the user, the PAM module tries to unlock the ‘login’ keyring with the password entered by the user. If the ‘login’ keyring does not exist it is created with the user’s password.