Bug #476
open
Bug #465: Issues with the development version
Gnome keyring never answers user's passwords
60%
Description
Gnome keyring is supposed to be started with the user's session in order to serve passwords to applications. However when using it for Wifi passwords, the password is asked every time the user enters his session. Investigations showed that it doesn't seem to be really working, although the daemon is active. Gnome keyring documentation is available online:
http://live.gnome.org/GnomeKeyring
with a dedicated page for Automatic Unlocking / PAM:
Updated by Jean-Michel Philippe about 13 years ago
Investigations showed that gnome-keyring-daemon is not started with sessions. It seems the package responsible for starting it is libpam-gnome-keyring. We would then just have to add it to the list of packages to be installed.
NB: configuration files in /etc/pam.d/ have changed between Lenny and Squeeze. We have to update them.
Updated by Jean-Michel Philippe about 13 years ago
The issue seems to be that gnome-keyring-daemon relies on user's session password to open the keyring, while we've disabled passwords. It is possible to remove keyring files in ~./gnome2/, re-activate passwords, enter the session to have the keyring create its files, re-disable passwords in /etc/pam.d/common-auth and /etc/pam.d/common-account, then logout. Next login will not require password authentication but the keyring will ask it.
The only solution for DDL could be to start the keyring feeding the password in our custom session script (and thus remove libpam-gnome-keyring).
Updated by Jean-Michel Philippe almost 13 years ago
- Due date changed from 11/30/2011 to 02/20/2012
- Target version changed from 2011-11 to 2012-02