On 5/27/2006 2:33 PM, Giovanni Bajo wrote:
> Duncan Murdoch wrote:
>
>>> I didn't try 2.0.58; should I? I *could* probably get them all to
>>> install cygwin & do
>>> the public key thing but would rather not if I can escape this.
>> Putty can also handle public keys, and serve as the ssh client: it's
>> probably less trouble to install than Cygwin. (Not that Cygwin is all
>> that difficult, but it's a lot bigger than Putty, and if someone
>> doesn't like *nix, they probably won't like Cygwin.)
>
>
> I'll second this. There are a few obvious advantage in using Putty over
> OpenSSH:
>
> - It doesn't require a cygwin installation, which is space on the disk, and the
> execution overhead of cygwin1.dll. People might mind.
> - There is a ssh agent which really works, and has a simple GUI to use it.
> Setting up the ssh-agent in cygwin is almost impossible, as you'd need to
> modify global environment variables for the account to make it work everywhere.
> I used to have a python script to do that (writing the registry) but it's a
> pain in the neck.
It's a bit of a pain in the neck, but not that bad. I just write the
process number to a file, and have my bash startup script source that
file, then restart the agent if the process doesn't seem to be there any
more.
It's only available from within bash, but I don't think any non-Cygwin
apps work with it anyway (TortoiseSVN doesn't). I like having ssh, sftp
and scp available in their command line versions within bash. I guess I
could fake them with Putty, but I just end up with both Pageant and
ssh-agent going most of the time.
Duncan Murdoch
> Configuration is very easy: it's sufficient to register plink.exe as the ssh
> tunnel in the Subversion config file (within the local Application Data
> directory).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 27 23:56:34 2006