In theory, if the puTTY ssh config is working, you should be able to hook up via the inclusion of a 'load ' on the TortoisePlink command line you drop into the Settings->Network->SSH Shell entry.
The SVN on the server can be perfectly OK and viable, yet the TortoiseSVN hookup craps out gloriously.
You'd access this with an svn+ssh:// URL.Ī couple of issues here - there are some fairly intricate certificate/PVT key operations which while perfectly acceptable for plink/pageant may be going haywire. This also requires some wrangling to get the SSH connectivity working - last time I messed with it it involved feeding tortoise the plink.exe file from PuTTY. But, since it's using the linux users, you'll need to jump through some hoops to lock down any user that you want to have SVN access but not shell access. This option uses the SSH setup that you've probably already got configured in this way it gets good authentication and encryption. You can configure security (authentication and encryption) in the web server, as well as access controls this is probably the most flexible of the options for this reason. This option requires a web server - probably Apache, with the mod_dav_svn module. You'd run the service (which is probably installed already on your server) and then run the checkout with an svn:// URL. It's pretty basic it can enforce permissions settings but has no encryption for its network traffic (including passwords). This is a simple service that runs on port 3690 that allows access to your repository. You'll need something to serve the repository to remote nodes.