DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=P6ufiChZqcz/UD0+oYixILcWykmDRAaBylP0IHTqEN2qS++CduuR0
	bJs8GtXr35Oz4rIvvgep44zPJuM7GT/Ijsqebt99io9M8gtoGHKv+Ur+etHVzwKf
	z7WvpEDvMzOJRCfVHziOQdRr96BgSm12WKwX6z1wsXgPJw9rOFWMQA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 8 Oct 2014 15:52:13 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with X86_64 ssh-agent
Message-ID: <20141008135213.GG29235@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <541482E3 DOT 4010503 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="NPukt5Otb9an/u20"
Content-Disposition: inline
In-Reply-To: <541482E3.4010503@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--NPukt5Otb9an/u20
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sep 13 10:46, DJ Sylvester wrote:
> I moved from 32- to 64-bit Cygwin (fully uninstalled 32, then installed
> 64). Since, I've spent days trying to get ssh to work. Just can't get the=
re.
>=20
> $ ssh -V
> OpenSSH_6.6.1p1, OpenSSL 1.0.1i 6 Aug 2014
>=20
> $ ssh-agent bash (also tried "eval `ssh-agent -s`")
>=20
> $ ps -ef | grep ssh
>     Boss    4404    7032 ?        10:07:11 /usr/bin/ssh-agent
>=20
> $ env | grep SSH
> SSH_AGENT_PID=3D4404
> SSH_AUTH_SOCK=3D/tmp/ssh-4KHvOMi6LAdi/agent.7032
>=20
> $ ls -al /tmp/ssh* | grep agent
> srw-------  1 Boss None 0 Sep 13 10:07 agent.7032=3D
>=20
> $ ssh-add
> Could not open a connection to your authentication agent.

Are you using a Cygwin developer snapshot by any chance?  There
was a bug in the 2014-08-18 snapshot triggering this problem.
Other than that, it works fine for me.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--NPukt5Otb9an/u20
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUNUGNAAoJEPU2Bp2uRE+g4hUP/36rFLpcPl0NV3yjlOWQCZz5
UmNV2TsZax9HVcujDAA7CaU5yVc6msf8EZLS/0HiezJiddf3PtJ3h2N2mPfK4bdq
8nrCWgNxgCmyiYtO/vgDm3QprPXMGCSvB02eyG4iYNCFP2COYQ9pU0mzGb4GTeKi
vTa749iDqf11ntEIyf6QV37rCW5D+DUD/XUOOFc/VIbh71+R3dQ5L2jiG6RqZfq8
5EZzKy6E7MyF5mZyTSh9ddQU9VD8HgA1RJhpU+a05Vmyc08c6odTz52d5ZEIn70z
R45VXYldhHs7CPJNZMavt4DnnHljLbe/qFYQNGzj0dtZENo2RuSc7/p0N/vAVK/t
yFrs2juJnL2aZHYtSg3aB5T1IMa5ifa1a96LLHK9EamT+N9f8dlRmAQKP22ZHmes
GQ8739zbE1dmhrxuHPKyJpO5lUoJJdPiGIso15ocuwxo9YEzeEwjnQKdmfyWRIra
37X1WjbMONY+GRbg6alKg4Yl2/bSJm9FhW4OeX9vys9lw+pTZeSwVAjEozUQ/9qE
OchPjSaY6IczJTekEqA6FyJ4sZJVUVOXpntympt33tZIgK4ECqLmCtBnDiQbW04C
Tvv2Ii/crvmVex9ZVJuHRivydHWPC50z24BFrCU5t3wfmAAbFLwwf5UwmoSkX5DX
TKiiBakOeWbICBbbgdV+
=p/so
-----END PGP SIGNATURE-----

--NPukt5Otb9an/u20--