Comment 47 for bug 932177

Revision history for this message
In , Guido Berhoerster (gber) wrote :

(In reply to comment #15)
> (In reply to comment #14)
> > Fixed in Factory.
>
> it's back again in 12.3-RC1 (or never got fixed?) !
>
> I'm using 12.3-RC1 plus updates and run XFCE4.
>
> /usr/bin/gnome-keyring-daemon --daemonize --login
>
> gets started and it's loading offering all my ssh-keys, which is a no-go!
>
> when debugging my ssh-agent problems, I found the hint in some discussions to
> rename/remove nome-keyring-daemon (or remove execute permission).
>
> this worked fine for me -- until bug #805048:
> NetworkManager needs gnome-keyring-daemon to ask for wifi passphrases :-((
>
> so gnome-keyring-daemon is back in businees, and trashes my ssh usage:-(
>
> looking for other solutions I found e.g.
> http://ubuntuforums.org/showthread.php?t=1655397
>
> but
>
> sudo gconftool-2 --direct --config-source
> xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set
> /apps/gnome-keyring/daemon-components/ssh FALSE
> does not help.
>
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/932177/comments/20
>
> does not work either for me, the key daemon still loads/offers all ssh keys
> (output of "ssh-add -l").
>
>
> for now I've hacked the gnome-keyring-daemon to garble the path to my keys:
>
> diff <( strings /usr/bin/gnome-keyring-daemon~ ) <( strings
> /usr/bin/gnome-keyring-daemon )
> 9543c9543
> < ~/.ssh
> ---
> > ~/@ssh
>
>
> but of corse that's not the way to go:-(
>
>
> so my question for running XFCE4:
>
> how can I disable the ssh-agent functionality for gnome-keyring-daemon these
> days ???

That's currently not possible, you can either start all components of gnome-keyring-daemon (by enabling GNOME compatibility mode) or not start it at all. This bug was about making it work properly at all which has been the case since 12.1. The ability to selectively enable/disable components is a different issue and would need to be addressed upstream. Please file a new enhancement request, preferably on the upstream tracker or here if you want me to forward it for you.