<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>crazed &#187; ssh</title>
	<atom:link href="http://www.crazed.org.uk/tag/ssh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.crazed.org.uk</link>
	<description>Musings of a web developer</description>
	<lastBuildDate>Sat, 22 Oct 2011 15:14:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Using svn+ssh in TortoiseSVN over a custom port</title>
		<link>http://www.crazed.org.uk/2010/06/using-svnssh-in-tortoisesvn-over-a-custom-port/</link>
		<comments>http://www.crazed.org.uk/2010/06/using-svnssh-in-tortoisesvn-over-a-custom-port/#comments</comments>
		<pubDate>Wed, 23 Jun 2010 19:21:19 +0000</pubDate>
		<dc:creator>Fai</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[putty]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[subversion]]></category>
		<category><![CDATA[tortoisesvn]]></category>

		<guid isPermaLink="false">http://www.crazed.org.uk/?p=148</guid>
		<description><![CDATA[Just discovered this &#8211; to connect to subversion over a SSH tunnel that&#8217;s not on the usual port 22, you need to save a PuTTY session using the custom port, and refer to the session name in place of the hostsname in TortoiseSVN. It seems whilst TortoiseSVN accepts the usual svn+ssh://myhost/repository/path URI (and even the [...]]]></description>
			<content:encoded><![CDATA[<p>Just discovered this &#8211; to connect to subversion over a SSH tunnel that&#8217;s not on the usual port 22, you need to save a PuTTY session using the custom port, and refer to the session name in place of the hostsname in TortoiseSVN.</p>
<p>It seems whilst TortoiseSVN accepts the usual <code>svn+ssh://myhost/repository/path</code> URI (and even the <code>svn+ssh://name@myhost/repository/path</code> variation), this assumes that SSH is running on the usual port 22. I have tried (using port 333 as an example) <code>svn+ssh://myhost:333/repository/path</code> and <code>svn+ssh+333://myhost/repository/path</code>, however these will cause a host not found error.</p>
<p>It turns out that TortoiseSVN accepts a session name in place of &#8216;<code>myhost</code>&#8216;, and the session name can include characters such as &#8220;<code>:</code>&#8221; so this would be one way of making the innocent looking <code>svn+ssh://myhost:333/</code> work!</p>
<p>i.e. create a PuTTY session named &#8216;new-sess:ion2&#8242; using the SSH protocol connecting to port 333 &#8211; and this should work in TortoiseSVN:  </p>
<p><code>svn+ssh://new-sess:ion2/repository/path</code></p>
<p> &#8211; or a session named  mysession:333  &#8211; </p>
<p><code>svn+ssh://mysession:333/repository/path</code></p>
<p>Now thankfully I do not have to be at home to view log information!</p>
<p>Reference: http://svn.haxx.se/tsvnusers/archive-2007-01/0272.shtml</p>
]]></content:encoded>
			<wfw:commentRss>http://www.crazed.org.uk/2010/06/using-svnssh-in-tortoisesvn-over-a-custom-port/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

