X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=JC2UTdtoqCF43gHbo2DxuhQnUOyfInZA7OsdoZcDSoY
	hx9ZbiKD5YPoMdWLj72pSSwFGF2Ks3wHApbB2Z2aUMSl8y4laNdJ6MvlcsyIpN44
	+i+ExGfl371faF4VNIXmgJZK1C8ENXQxreplcbW1TgSSziPdR0Y06+iw0xoFBxxI
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=NEKQK8M/KTpe/l4ckay4/ed28tU=; b=ayt/+MwI014D+NGEu
	EjLTXfr2YFZTyXW36oRwSUzA2oOc78yjtKtRsduxYpaMd4Z7/DAEN0gsE6RGN2Xl
	056n9Cqr6rh0Z7JI7tFwV5kmSO/l6TFH/X2w33JSmD3mQUztqjGzRIiIbmjkp1tP
	GElyDDX2WSVTMAGAFShLEe30TU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	BLU004-OMC1S22.hotmail.com
X-TMN:	[fYbltcu425kHwOt/jEqXRt60TVX1TdWj]
Message-ID:	<BLU436-SMTP2568C2C9833376660DD60CAE4A10@phx.gbl>
Date:	Fri, 10 Oct 2014 22:11:41 +0700
From:	Alive <alive4ever AT live DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Problem with X86_64 ssh-agent
References:	<541482E3 DOT 4010503 AT gmail DOT com> <20141008135213 DOT GG29235 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20141008135213.GG29235@calimero.vinschen.de>
X-IsSubscribed:	yes

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

- Raw text -