[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Help with Svn via SSH

From: Thomas Harold <tgh_at_tgharold.com>
Date: 2006-10-18 03:57:46 CEST

Chris.Fouts@qimonda.com wrote:
> I played with this a little more, along with coaching from
> Erik. The trick is to
> - Add plink.exe to your global path variable
> - set SVN_SSH=plink -ssh -l user -pw password

Interesting, I've been playing with this lately as well. We use
TortoiseSVN with URLs like:


The private key gets loaded into PAgent so that TortoiseSVN can access
it. That works fine, but sometimes we want to use the command-line
client as well on the same working copy.

For the Win32 command-line client, we added C:\Program Files\PuTTY to
the PATH variable like you suggested. But we are able to use a simpler
SVN_SSH variable of just "SVN_SSH=plink".

But that could be because I didn't bother to protect my SVN SSH key with
a passphrase. (A moderately risky move, but a calculated risk in our

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 18 03:58:33 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.