On Wed, 28 May 2008 03:12:37 +0200 Josselin Mouette <[EMAIL PROTECTED]> wrote:
> > This is indeed done with a specific PAM module. > > The data is stored in a file encrypted with AES128 using the login > password. > I've spent some effort in configuring PAM to use libpam-ssh through GDM. I use KDE, really. Now I have ssh-agent and gnome-keyring fighting over keys, in KDE, while I did configure my system to use ssh-agent already. This is a bit irritating, and probably shouldn't occur. Why is gnome-keyring running in KDE? Is this a Freedesktop move or a (too lenient) dependency problem in Debian? Shouldn't there be some dependency conflict between the ssh-agent and gnome-keyring packages then? Or between libpam-ssh and gnome-keyring? This way it's causing a lot of confusion and undoing whatever configuration people have already done on their machines with ssh-agent or libpam-ssh. I'm disabling gnome-keyring ssh-agent functionality for now (for reference): # gconftool-2 --set -t bool /apps/gnome-keyring/daemon-components/ssh false ... but it might be best to let the package system clear up the confusion between some of the above mentioned packages by conflicting. Thanks for your help though! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
