This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problem with X86_64 ssh-agent
- From: Alive <alive4ever at live dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 10 Oct 2014 22:11:41 +0700
- Subject: Re: Problem with X86_64 ssh-agent
- Authentication-results: sourceware.org; auth=none
- References: <541482E3 dot 4010503 at gmail dot com> <20141008135213 dot GG29235 at calimero dot vinschen dot de>
It's fine. Maybe there are old sockets remaining on /tmp/ directory? Try
deleting all files and folders in the /tmp/ dir and relaunch ssh-agent.
I usually launch ssh-agent with this command
```
eval $(ssh-agent)
```
After launching ssh-agent with the above command, there are two
environment variables related to ssh-agent: SSH_AGENT_PID and
SSH_AUTH_SOCK. To verify that those environments are available, run this
command
```
env | grep -E SSH
```
You should see output similar to this
```
env | grep -E ^SSH
SSH_AGENT_PID=4416
SSH_AUTH_SOCK=/tmp/ssh-VRhorGk5KFI0/agent.5000
```
The rest is adding ssh keys to the agent.
```
ssh-add ~/.ssh/id_rsa
```
The added keys should be available for use with ssh in the same terminal
session.
If you intend to use the same ssh-agent instance on multiple terminal
sessions, you have to set the value of SSH_AGENT_PID and SSH_AUTH_SOCKS
according to the first ssh-agent instance.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple