Comments on: Hack It! #1 – Change the TortoiseSVN SSH port

By: TortoiseSVN, plink, and non-standard ports | AlexDuan.com

TortoiseSVN, plink, and non-standard ports | AlexDuan.com — Wed, 17 Aug 2011 04:25:46 +0000

[...] doesn’t like connecting over ssh+svn using non-22 ports. Instead of the inflexible hack shown here, I prefer this hack. The bat script that worked for [...]

By: Michael Holroyd

Michael Holroyd — Tue, 31 May 2011 19:34:52 +0000

Thanks! The worst part about this is that TortoiseSVN doesn’t even throw and error at connections with :port at the end. How is anyone supposed to know it is ignoring this standard convention?!

By: k00pa

k00pa — Sun, 30 May 2010 12:16:56 +0000

THANK YOU!

I was just looking for this trick Why the putty/plink can have the “:3445″ port support why default :/

By: Martin

Martin — Tue, 04 May 2010 09:38:49 +0000

Thanks a lot, i wasted hours on this issue.. the solution was that easy…

it works fine now!

By: Gøran

Gøran — Fri, 10 Apr 2009 18:33:46 +0000

Thanks for the tip! This led me to try for a more dynamic solution and I’ve tried a different approach, it seems to work (“seems” cause I’ve only tested it against one subversion server). The help message for putty link (and thereby TortoisePlink.exe), states that “host” in the url may be a saved Putty session. This means that you can save a putty session towards your nonstandard ssh server as e.g. “mysvn” using a different ssh port, and then use a standard svn+ssh url to access it, e.g: svn+ssh://user@mysvn/svn/code

By: Stuart

Stuart — Sun, 15 Feb 2009 14:28:00 +0000

Thanks for this, works great – I’ve copied your blog and put into mine, changed a few things to point to 443 as a port – but I’ve credited you for this and I reference this on the post.

ref : http://www.opensource-knowledge.com/?p=45

By: Opensource knowledge » Blog Archive » Tortoise SVN port ssh change 443

Opensource knowledge » Blog Archive » Tortoise SVN port ssh change 443 — Sun, 15 Feb 2009 11:43:30 +0000

[...] Hack It! #1 – Change the TortoiseSVN SSH port [...]

By: the__phoenix

the__phoenix — Mon, 13 Oct 2008 11:40:09 +0000

Thank you very much for this hack!

By: Unformatt

Unformatt — Tue, 19 Aug 2008 18:52:26 +0000

Thanks for this - I created a batch script which you can point Tortoise at and it will pluck out the port for you and pass it to TortoisePlink http://unformatt.com/news/non-standard-ssh-ports-with-tortoise-svn/

By: peter

peter — Fri, 08 Aug 2008 07:41:17 +0000

Hi Arthur,

Thanks for the correction regarding the cause of the issue – good point. The fault lies with TortoiseSVN rather than the actual protocol.

You’d think it would be a relatively easy fix, but in the meantime, just Hack It! (TM)