This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [ITP] win-ssh-agent 1.07

> Date: Thu, 3 Nov 2011 23:03:39 -0400
> From: cgf
> To: cygwin-apps
> Subject: Re: [ITP] win-ssh-agent 1.07
> 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.
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.
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.
if [ -z "$SSH_AUTH_SOCK" ]; then
 export SSH_AUTH_SOCK="$HOME/.ssh/ssh-auth-sock"
ssh-add -l &>/dev/null
if [ $ec -eq 2 ]; then
 rm $SSH_AUTH_SOCK &>/dev/null
 ssh-agent -a $SSH_AUTH_SOCK &>/dev/null
elif [ $ec -eq 1 ]; then
You can also define SSH_AUTH_SOCK in the registry if you wish for non-Cygwin uses.
So I don't see a need for win-ssh-agent, unless the OP can identify any use cases not
satisfied by existing options?

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]