Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 130239 - ssh-agent SSH_AUTH_SOCK: agent filename is wrong.
Summary: ssh-agent SSH_AUTH_SOCK: agent filename is wrong.
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Andrea Barisani (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-17 03:49 UTC by Yongsub Chung
Modified: 2010-07-01 14:15 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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).