Bug#524018: openssh-client: ssh-agent as started by xsession can't use keys

[Jon Dowland <jon+bts@alcopop.org>]

On Tue, Apr 14, 2009 at 12:01:17PM +0100, Colin Watson wrote:
> Are you sure that OpenSSH's agent is in fact the one being used here?  GNOME
> has recently taken to using "seahorse" which has some bugs.
> 
> You can tell the difference by typing 'echo $SSH_AUTH_SOCK'. A genuine
> OpenSSH agent will be "/tmp/ssh-SOMETHING/agent.PID".

Strange. As below, this suggests that this is indeed seahorse, or at least not
ssh-agent. The SSH_AGENT_PID matches up with a /usr/bin/ssh-agent and I don't
think seahorse (or anything else) is faking itself as /usr/bin/ssh-agent, there are no alternatives or diversions in place either.

	13:59:29$ echo $SSH_AUTH_SOCK
	/tmp/keyring-IrOybQ/socket.ssh
	13:59:32$ echo $SSH_AGENT_PID
	3482
	13:59:35$ ps -eaf|grep 3482
	jon       3482  3428  0 10:13 ?        00:00:00 /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/jon/.gnupg/gpg-agent-info-ra /usr/bin/dbus-launch --exit-with-session x-session-manager
	jon      13182 13151  0 13:59 pts/5    00:00:00 grep 3482
	13:59:38$ ls /tmp/ssh-ISulua3428/agent.3428 
	/tmp/ssh-ISulua3428/agent.3428
	13:59:45$ ps -eaf|grep 3428
	jon       3428  3273  0 10:13 ?        00:00:00 x-session-manager
	snip

I've just removed seahorse, logged out, restarted gdm, logged back in again and the problem remains, so it probably isn't actually seahorse, but it most likely isn't ssh agent either. Do you mind if I park this report here regardless until I've figured out a better place for it?

	11:14:35$ ps -eaf|grep ssh-agent
	jon      22681 22627  0 11:12 ?        00:00:00 /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/jon/.gnupg/gpg-agent-info-ra /usr/bin/dbus-launch --exit-with-session x-session-manager
	11:14:36$ export | grep SSH
	declare -x SSH_AGENT_PID="22681"
	declare -x SSH_AUTH_SOCK="/tmp/keyring-n23XSa/socket.ssh"