Bug#471122: seahorse force-loads ssh keys that are already loaded

Wouter Van Hemel debian at publica.duodecim.org
Sat May 24 03:30:49 UTC 2008


On Sat, 24 May 2008 03:59:55 +0200
Josselin Mouette <joss at debian.org> wrote:

> Le samedi 24 mai 2008 à 02:58 +0300, Wouter Van Hemel a écrit :
> > Hello,
> > 
> > I understand you might be very busy, but have you already had a
> > chance to track down why this dialog pops up and requests to unlock
> > already unlocked keys?
> 
> Actually this doesn’t come from seahorse but from gnome-keyring.
> gnome-keyring-daemon completely replaces ssh-agent and as such will not
> use the unlocking you’ve done in PAM. However, if you decide to store
> the passphrase in the “login” keyring, it will be automatically unlocked
> upon login as well.
> 

How does that work? Do I have to type the password seperately upon login,
does gnome-keyring link to GDM/PAM, or does it store the password on disk?

Perhaps there's a gnome-keyring PAM module being planned?

> Cheers,

Thanks for your help,

  Wouter






More information about the pkg-gnome-maintainers mailing list