From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32126 invoked by alias); 6 Nov 2011 05:21:44 -0000 Received: (qmail 32112 invoked by uid 22791); 6 Nov 2011 05:21:42 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,TW_CG X-Spam-Check-By: sourceware.org Received: from col0-omc4-s7.col0.hotmail.com (HELO col0-omc4-s7.col0.hotmail.com) (65.55.34.209) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 06 Nov 2011 05:21:29 +0000 Received: from COL102-W12 ([65.55.34.200]) by col0-omc4-s7.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sat, 5 Nov 2011 22:21:29 -0700 Message-ID: From: Karl M To: Subject: RE: [ITP] win-ssh-agent 1.07 Date: Sun, 06 Nov 2011 05:21:00 -0000 In-Reply-To: <20111104030339.GB7994@ednor.casa.cgf.cx> References: ,<20111104030339.GB7994@ednor.casa.cgf.cx> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2011-11/txt/msg00034.txt.bz2 > Date: Thu, 3 Nov 2011 23:03:39 -0400 > From: cgf > To: cygwin-apps > Subject: Re: [ITP] win-ssh-agent 1.07 >=20 > I don't agree. I don't see why this couldn't be accomplished using > standard UNIX tools and it seems like it might even be a potential > security hole. I don't see the need to have this package in the > distribution. >=20 I have been using ssh-agent with the -a option to explicitly specify the socket instead of the randomly chosen socket name. This avoids the slow execution of keychain and simplifys the location of the socket. =20 The below is from my .bash_profile to launch the agent as needed. The initial test of SSH_AUTH_SOCK is to support a forwarded agent. =20 if [ -z "$SSH_AUTH_SOCK" ]; then export SSH_AUTH_SOCK=3D"$HOME/.ssh/ssh-auth-sock" fi ssh-add -l &>/dev/null ec=3D$? if [ $ec -eq 2 ]; then rm $SSH_AUTH_SOCK &>/dev/null ssh-agent -a $SSH_AUTH_SOCK &>/dev/null ssh-add elif [ $ec -eq 1 ]; then ssh-add fi =20 You can also define SSH_AUTH_SOCK in the registry if you wish for non-Cygwi= n uses. =20 So I don't see a need for win-ssh-agent, unless the OP can identify any use= cases not satisfied by existing options? =20 Thanks, =20 ...Karl=20=09=09=20=09=20=20=20=09=09=20=20