[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: svn+ssh on mingw32?

From: Sheldon Gill
Subject: Re: svn+ssh on mingw32?
Date: Wed, 08 Feb 2006 19:15:20 +0800
User-agent: Thunderbird 1.5 (Windows/20051201)

Richard Frith-Macdonald wrote:

On 8 Feb 2006, at 10:45, Sheldon Gill wrote:

Richard Frith-Macdonald wrote:
I expect so ... but the question is ... why?
My ssh connection works fine.
svn+ssh works fine on linux.
So the issue must be something to do with the subversion client ... my guess is it's not picking up the ssh configuration from ~/.ssh for some reason, but I haven't figured out how/why that can be the case. I also don't see how a problem with the command-line client could also effect the TortoiseSVN stuff ... which I configured completely independently using Putty stuff rather than OpenSSH stuff. That's two different ssh implementations being used and both giving the same error.

Maybe this will help:

export SVN_SSH=ssh -l rfm -i ~/.ssh/your_key

Thanks ... but I've just now got it working, and I'm inclined to stick with what I've got.

I edited 'C:/Documents and Settings/richard/Application Data/Subversion/config' and added a line to explicitly specify the path to my mingw32/msys copy of ssh ...

'ssh = $SVN_SSH C:/msys/1.0/bin/ssh.exe'

Actually, editing [tunnels] in subversion config was my next suggestion.

For what its worth, here's a summary for getting PuTTY going:

* download and install svn client
* download and install putty, plink, pageant...

  Make sure both are in your path somewhere. I like \Program Files\Bin\

* Generate a key using puttygen
  (It can also import existing keys from elsewhere...)
  Save it somewhere as <keyfile.ppk>

* Tell about the key and wait an hour
* Check ssh access

  plink -v -ssh -l <username> -i <keyfile.ppk>

* Edit Subversion configuration %USERPROFILE%\Application Data\Subversion\config

  putty = plink -ssh -l <username>

* Launch pageant and add your key

* Check subversion access

  svn list svn+putty://


reply via email to

[Prev in Thread] Current Thread [Next in Thread]