This part is very easy if you are using gnome and gdm. But the part that I use kdm and nm-applet uses keyring made matters worse for me. As of now nm-applet is the only decent UI for network manager.
So after hours of search and reading existing bug reports I arrived at the solution for me. Though I am using ubuntu I got the solution from a fedora bug report.
First we need to edit /etc/pam.d/kdm . I added these to it
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start
Also the important part is if you have been already using gnome-key-ring by default your data such as wifi WEP2 key will go to the default keyring. This make this setup fail. So you need to delete the existing keyrings. So that new ones will go to login keyring.
What I am frustrated is that there is no consistent way for kdm users to use this feature. It took me hours of frustrating searching to arrive at this working set up.
3 comments:
Been having the same problem... Thanks... Hope this work. Trying now on Fedora 11 - KDE 4
I followed the guide at: http://live.gnome.org/GnomeKeyring/Pam
But instead of making those entries into the specified gnome files, I made it to the corresponding kde files.
So I made entries to /etc/pamd.d/ -
- kde
- kscreensaver
- passwd
and it worked just fine. I didn't have to delete any of the gnome files, and the previous keyring entries persisted (so I guess that means both kde and gnome are sharing the same keyring now?) I don't know if this is due to updates though. I'm using Arch Linux, kde 4.4.3, and gnome 2.30.0.
Thanks, it works for me too.
One more note for Ubuntu 10.04, that lines should be added at the end of file (after @include common-password).
Post a Comment