Bug#735664: openssh-client: ssh-agent gets duplicate keys, breaks ssh-add

[Francois Gouget]

On Fri, 17 Jan 2014, Timo Weingärtner wrote:
[...]
> This looks like you're using ssh-add from openssh-client, but gnome-keyring
> as ssh-agent (not the one from openssh-agent).

I do have a gnome-keyring process:
$ ps aux
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
fgouget   4170  0.0  0.1 586348  4456 ?        Sl   00:39   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login

However I also have an ssh-agent process and the environment points to 
that process:

$ env | grep SSH_
SSH_AGENT_PID=4229
SSH_AUTH_SOCK=/run/user/1000/keyring-o10tSl/ssh
$ ps aux
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
fgouget   4229  0.0  0.0  10444   328 ?        Ss   00:39   0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/lib/gnome-panel/gnome-session-flashback
$ ll /usr/bin/ssh-agent
-rwxr-sr-x 1 root ssh 127K déc.  23 13:19 /usr/bin/ssh-agent
$ dpkg -S /usr/bin/ssh-agent
openssh-client: /usr/bin/ssh-agent

So ssh-add should really connect to the openssh ssh-agent process and 
not to gnome-keyring-daemon. Or is the latter somehow hijacking the 
former?


Also, just to be clear, I did not tweak this ssh-agent/gnome-keyring 
configuration. So this is not a rare special case that arises out of 
imprudent configuration changes, but is rather how things are by default 
with GNOME (at least Flashback) in Debian Testing (and 6 and 7 according 
to limited tests).


-- 
Francois Gouget <fgouget at free.fr>              http://fgouget.free.fr/
       Be careful of reading health books, you might die of a misprint.
                                 -- Mark Twain