GNOME Bugzilla – Bug 523470
SSH keys not unlocked when started from the .service file
Last modified: 2008-03-26 10:00:24 UTC
Hi, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471270 When started from the dbus .service file g-k-d does not unlock SSH keys as the ssh component is not started: [...] Exec=/usr/bin/gnome-keyring-daemon --foreground --components=keyring [...] Adding ",ssh" at the end fixes this but I have a feeling that there should not be any components given at all. gkr-daemon.c has #define DEFAULT_COMPONENTS "ssh,keyring,pkcs11" (the --help text is wrong btw, it only mentions the first two) and it says that the components to load are read from gconf so instead of forcing only "keyring" in the service file this should better be handled automatically (i.e. gconf and enable-all-fallback). Ok to commit one of the attached patches? :)
Created attachment 107650 [details] [review] g-k-d-default-components.diff Automatically detect which components to start
Created attachment 107651 [details] [review] g-k-d-enable-ssh.diff Enable keyring and ssh components in any case
Marking this as blocker because it makes g-k more or less useless unless started from gdm via pam.
Created attachment 107652 [details] [review] help-text.diff Fix the help text
gnome-keyring-daemon should be started from PAM or gnome-session. When started from the service file it only functions for storing passwords, all other functionality is not available. Here's a little overview: http://live.gnome.org/GnomeKeyring/Distributors