TortoiseSVN The coolest Interface to (Sub)Version Control

When trying to log in, I kept getting an "Invalid Port Number" from putty.

The message comes up if the user has already made an SSH connection using the Putty saved session. To avoid the error, you need to use a "Saved Session" that has never been used before.

If that doesn't work:

• leave the SSH client field blank (which makes TortoiseSVN use TortoisePlink)
• when you enter the URL of the repository, use the name of the saved session. For example, if your session name is MyConnection, use MyConnection instead of e.g. www.example.com

This walkthrough on getting SVN+SSH up and running on a Windows Box was provided by Thorsten Möller
Thanks!

Hi all,

I just want to provide my solution to the community since I have found out that there might be many people struggling with the same issue.

1. Server: Install Cygwin SSH daemon as described here: http://pigtail.net/LRP/printsrv/cygwin-sshd.html
2. Install SVN on the server (as described in the Subversion doku)
   
   

Sent to the TortoiseSVN mailing list by Nigel Green, Thanks!

The final workaround that I came up with may well be helpful to others trying to solve the same problem, so I thought it worthwhile to detail my findings below ........

What I was trying to achieve was a single server containing 2 virtual SSL hosts: The first one was for public access, with no requirement for a client certificate. The second one was to be totally secure with a required client certificate, running a Subversion that I could access with TortoiseSVN.

Since SSH completely takes care of the authentication process, Subversion won't even see the author who does the commit. So to tell Subversion an author you have to specify the author in the URL itself. E.g. svn+ssh://username@server.com.
You should do that when you check out your working copy.

TortoiseSVN (or better its SSH client TortoisePlink) can't find a key for the current user. Run pageant and add your private key or define a putty session with a private key included.
Try saving another copy of the key after clearing the passphrase and use that new key. Putty no longer prompts for a passphrase.

Add the directive SSLRequireSSL to your Subversion <Location> block in the Apache config file.

(revision 0.5 by (c) Marc Logemann)

Because many new subversion users run into problems when attempting to use subversion with SSH, I compiled a HowTo for that issue. Perhaps I will expand this HowTo later on and submit it to the Subversion or TortoiseSVN docs.

-------------------------
Our Scenario:
-------------------------
Server: Linux or unix like system
Client: Windows 2000/XP (or variant)

TortoiseSVN uses Subversion. And Subversion supports SSH svn+ssh:// (repository reachable via svnserve). If you don't want to use the svnserve server but Apache instead (which we would recommend!) then Subversion supports secure connections via SSL.

A guide on how to secure your Apache server with SSL can be found in the TortoiseSVN Daily Use Guide

Settings-Dialog, "Clear Auth Cache" button.