Bugzilla – Bug 416942
autologin session, unlock the default keyring prompt appears
Last modified: 2009-04-28 22:20:14 UTC
hello, i am using auto login session, but i still get the prompt on startup from my wireless network connection and have to enter password to unlock the default keyring, the user password and the wlan password are the same, see screenshot > cat /etc/pam.d/gdm #%PAM-1.0 auth include common-auth account include common-account password include common-password session required pam_loginuid.so session include common-session session required pam_resmgr.so auth optional pam_gnome_keyring.so auto_start session optional pam_gnome_keyring.so > grep -rq pam_gnome_keyring.so /etc/pam.* && echo "Have PAM Support" Have PAM Support > test -f ~/.gnome2/keyrings/login.keyring && echo "Have 'login' keyring" Have 'login' keyring what do i expect? i expect that autologin session unlocks the default keyring at startup, so the wlan connection can be established without asking me for password thank you
Created attachment 233196 [details] keyring prompt
IMHO this is not related to bug #383353
to #2: ok that was my bad then...
I agree that this is a bug but unfortunately it's probably impossible to solve at present. You need a password to unlock the keyring. Autologin doesn't use a password so there's no password for pam to give to the keyring daemon. The workaround is to not use autologin.
to #4: Andrew, is it at least fixed in Opensuse 11.1?
Not fixed for 11.1, nor can it be to keep your password secure unfortunately, otherwise you'd give access to all your passwords trivially.
This works under 11.0 and fails under beta-5. It may not be correct but I copied the two keyring files from my home directory on 11.0 to 11.1 and it works.
It's definitely not something that is fixable, unless the user decides to use an empty password for the keyring. But if you use autologin and you have a password on your keyring, there's no way the keyring can be unlocked without asking for the password (where could it find the password?) So it's really not a bug.