svn+ssh port handling...

[Roman K]

I have running my ssh server on non-standard port and when I use svn+ssh://
me@myserver:port/path/to/repo i cannot connect unles I explicitly specify

port to plink (under network settings) like

"C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe"  -P  xxxx

Previopus versions (up to 1.14.0) seemed to handle that properly fom url (:PORT part) so you could handle different repos on different servers with different ssh ports. But not now...

[Justin MASSIOT]

Hello Roman,

The standard way is to specify the port right inside the 'ssh' definition of the SVN configuration (which is then used by 'svn+ssh'), under the '[tunnel]' section.

I don't know if a port specified directly in the URL is supposed to work or not, even in older versions.This may be more of an SVN concern than something related to TortoiseSVN. Have you checked the SVN changelog?

Justin

[Valerio Bozzolan]

I noticed that other proprietary SVN clients like SmartSVN just work out of the box handling such URLs:

svn+ssh://user@host:port/path

I think this feature is very strategic to avoid abandoning TortoiseSVN.

My working reality has shown it. My colleagues using  Windows migrated from TortoiseSVN to SmartSVN when the company adopted a custom SVN port on our Phabricator.

The company has no intention of changing ports and Windows users have no intention in handling weird configurations. As the result, proprietary software sadly win again.

[Justin MASSIOT]

Stefan,

I suppose this topic is related to the underlying svn tool and TSVN is not responsible in any way but... can you please give us some information about what is the standard behaviour?

Is it expected that a specific port provided directly in the URL is not handled correctly?

Justin