Re: Help with Svn via SSH

[Thomas Harold <tg...@tgharold.com>]

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:

svn+ssh://thomas@svn.example.com/var/svn/repos-jobs

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 
environment.)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Help with Svn via SSH

[Ch...@qimonda.com]

 

>-----Original Message-----
>From: Thomas Harold [mailto:tgh@tgharold.com] 
>Sent: Tuesday, October 17, 2006 9:58 PM
>To: Fouts Christopher (QNA RTP PT PREV)
>Cc: users@subversion.tigris.org
>Subject: Re: Help with Svn via SSH
>
>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:
>
>svn+ssh://thomas@svn.example.com/var/svn/repos-jobs
>
>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
>environment.)
>

Yep that's why you get by with the simpler SVN_SSH variable.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org