From: Karl M <karlm30@hotmail.com>
To: <cygwin-apps@cygwin.com>
Subject: RE: [ITP] win-ssh-agent 1.07
Date: Sun, 06 Nov 2011 05:21:00 -0000 [thread overview]
Message-ID: <COL102-W126165F47CFEE26CA5EA45B5D80@phx.gbl> (raw)
In-Reply-To: <20111104030339.GB7994@ednor.casa.cgf.cx>
> 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"
fi
ssh-add -l &>/dev/null
ec=$?
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
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?
Thanks,
...Karl
next prev parent reply other threads:[~2011-11-06 5:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 11:20 Nayuta Taga
2011-11-03 13:52 ` Andrew Schulman
2011-11-04 3:04 ` Christopher Faylor
2011-11-04 6:37 ` Nayuta Taga
2011-11-04 9:44 ` Corinna Vinschen
2011-11-04 14:06 ` Thrall, Bryan
2011-11-04 14:22 ` Eric Blake
2011-11-04 16:18 ` Nayuta Taga
2011-11-04 16:36 ` 多賀奈由太
2011-11-06 5:21 ` Karl M [this message]
2011-11-06 5:30 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=COL102-W126165F47CFEE26CA5EA45B5D80@phx.gbl \
--to=karlm30@hotmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).