Howto: Get Network Manager to stop asking you for your keyring password (pam_keyring)

[FishRCynic]

this works great - without beryl - when beryl loads the password is required again.
i have set up auto login which works as advertised with the pam keyring working well when
beryl is disabled. When beryl is enabled, the logon proceeds correctly the gdm call
does not request a password but as soon as beryl loads the nm-applet must get refreshed
and the keyring password is required. I have tried to enable a pam keyring configuration file
for nm-applet and/or for beryl but so far i have not been successful. If anyone can point me in the right direction it would be most appreciated.

[Pausanias]

Tested this on feisty and it works great. Thanks!

Just a note for feisty people:

to install on feisty:

sudo apt-get install libpam-keyring

to enable it:
1) edit /etc/pam.d/gdm

gksudo gedit /etc/pam.d/gdm

2) Add this line to the end

@include common-pamkeyring

[Durden]

This works great for when my laptop starts up (using Feisty) but when I hibernate and come back I have to enter my passphrase again. Anyone have a solution? This is the last annoying thing in my Ubuntu setup.

[craigmac]

I'm with Durden on this one. When my lappie comes back from suspend or hibernate, I need to enter the keyring password.

Anybody have a solution for this one?

[Thomaseov]

I'm with Durden and craigmac...I never had any trouble with wifi until feisty...it always just worked on my laptop at home, and I used the console to connect elsewhere with iwlist, iwconfig and dhclient. Now it is painfully slow and even with pamkeyring I still have to renter my password on waking from suspend after a 15 second wait... anyone?

[TomFumb]

ok this is not good, I did everything in this howto, to the letter, and now gdm won't work anymore

I can log in to the system in text mode with no problems, and I removed the 'x' from my username in /etc/passwd, but I still can't log in with gdm

does anyone know how to fix this problem? I already tried reinstalling gdm, and my /etc/pam.d/gdm file is back to how it was before I started with network manager.

I'd really hate to have to reinstall because of this

thanks

[h6w]

Try appending to /etc/pam.d/gdm-autologin the same couple of lines you appended to /etc/pam.d/gdm.

I haven't tried it myself, but it seems like it ought to work. However, if you do this, be aware that you're taking another step down the convenience-vs.-security spectrum.

Not quite. It will work, however, during the login process it will pop up a big text box saying "Automatic login password" with a field in plaintext (not password cloaked)!

[ngolian]

Several people have asked how to get this to work with autologin. Making the same change to /etc/pam.d/gdm-autologin as to /etc/pam.d/gdm described at the start of the thread sort of works, but you do get asked for a password at login, so it isn't really automatic any more.

Instead I wrote this script:

#!/bin/sh
exec echo -n "MyKeyringPassword" | /usr/lib/libpam-keyring/pam-keyring-tool -u -s

and added it to the session Startup Programs. Obviously it relies on being run after gnome-keyring-daemon starts but before nm-applet, but that seems to happen automagically for me.

So I don't need to enter a password at all any more! I know, I know, very lax security. But people who don't use gdm autologin might also find this method useful, because it means you can use separate passwords for logging in and for the keyring. And the script could probably be refined so as not to reveal the password in plain text.

You still need the libpam-keyring package for pam-keyring-tool. And I had to look at the source to find out how to use it. There's probably a way of doing the same thing using the dbus interface so you don't need libpam-keyring.

[Mr Squiddy]

Apologies if anyone has asked this one before but is there an equivalent change which can be done on Kubuntu to achieve the same end? I tried doing the same modification to /etc/pam.d/kdm as one would do for /etc/pam.d/gdm but it doesn't work.

[depp]

you can simply disable kwallet