Bug 130239

Summary:	ssh-agent SSH_AUTH_SOCK: agent filename is wrong.
Product:	Gentoo Linux	Reporter:	Yongsub Chung <litdream>
Component:	Current packages	Assignee:	Andrea Barisani (RETIRED) <lcars>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	base-system
Priority:	High
Version:	2006.0
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Yongsub Chung 2006-04-17 03:49:58 UTC

I found this when I installed new gentoo 2006.0 recently.
ssh-agent in current openssh-4.2_p1-r1 gave me this error.

-bash: SSH_AUTH_SOCK=/tmp/ssh-WlpOOS6703/agent.6703;: No such file or directory

A trailing semicolon became a part of SSH_AUTH_SOCK filename.
It is trivial, but manually exporting line without semicolon everytime when I call xterm isn't fun  :)

I appreciate who maintains gentoo linux.
This is the best linux distribution that I have ever used.

Comment 1 SpanKY gentoo-dev

2006-04-18 07:28:21 UTC

what are you trying to do exactly ?

proper usage of ssh-agent is something along the lines of:
eval $(ssh-agent)

Comment 2 Kevin Ernst 2010-07-01 14:15:28 UTC

The error received by the original poster is what happens when you invoke ssh-agent (incorrectly) like:

  `eval ssh-agent`

(Notice that the backticks are in the wrong place.) The man page states that should be, instead:

  eval `ssh-agent`

or, the equivalent:

  eval $(ssh-agent)

I'm adding this information to the bug report, because this bug happens to be very high in the search results for "ssh_auth_sock no such file or directory." So yeah, I made the same mistake, and the answer was here (or, evidently, also in the fine manual).