<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Hack It! #1 - Change the TortoiseSVN SSH port</title>
	<atom:link href="http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/</link>
	<description>that is also super</description>
	<pubDate>Wed, 10 Mar 2010 14:42:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Gøran</title>
		<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/#comment-4595</link>
		<dc:creator>Gøran</dc:creator>
		<pubDate>Fri, 10 Apr 2009 18:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/?p=16#comment-4595</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Thanks for the tip! This led me to try for a more dynamic solution and I&#8217;ve tried a different approach, it seems to work (&#8221;seems&#8221; cause I&#8217;ve only tested it against one subversion server). The help message for putty link (and thereby TortoisePlink.exe), states that &#8220;host&#8221; 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. &#8220;mysvn&#8221; using a different ssh port, and then use a standard svn+ssh url to access it, e.g: svn+ssh://user@mysvn/svn/code</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart</title>
		<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/#comment-4583</link>
		<dc:creator>Stuart</dc:creator>
		<pubDate>Sun, 15 Feb 2009 14:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/?p=16#comment-4583</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Thanks for this, works great - I&#8217;ve copied your blog and put into mine, changed a few things to point to 443 as a port - but I&#8217;ve credited you for this and I reference this on the post.  </p>
<p>ref : <a href="http://www.opensource-knowledge.com/?p=45" rel="nofollow">http://www.opensource-knowledge.com/?p=45</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Opensource knowledge &#187; Blog Archive &#187; Tortoise SVN port ssh change 443</title>
		<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/#comment-4582</link>
		<dc:creator>Opensource knowledge &#187; Blog Archive &#187; Tortoise SVN port ssh change 443</dc:creator>
		<pubDate>Sun, 15 Feb 2009 11:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/?p=16#comment-4582</guid>
		<description>[...] Hack It! #1 - Change the TortoiseSVN SSH port [...]</description>
		<content:encoded><![CDATA[<p>[...] Hack It! #1 - Change the TortoiseSVN SSH port [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the__phoenix</title>
		<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/#comment-2005</link>
		<dc:creator>the__phoenix</dc:creator>
		<pubDate>Mon, 13 Oct 2008 11:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/?p=16#comment-2005</guid>
		<description>Thank you very much for this hack!</description>
		<content:encoded><![CDATA[<p>Thank you very much for this hack!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unformatt</title>
		<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/#comment-1629</link>
		<dc:creator>Unformatt</dc:creator>
		<pubDate>Tue, 19 Aug 2008 18:52:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/?p=16#comment-1629</guid>
		<description>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

&lt;a href="http://unformatt.com/news/non-standard-ssh-ports-with-tortoise-svn/" rel="nofollow"&gt;http://unformatt.com/news/non-standard-ssh-ports-with-tortoise-svn/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>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</p>
<p><a href="http://unformatt.com/news/non-standard-ssh-ports-with-tortoise-svn/" rel="nofollow">http://unformatt.com/news/non-standard-ssh-ports-with-tortoise-svn/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/#comment-1548</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Fri, 08 Aug 2008 07:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/?p=16#comment-1548</guid>
		<description>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)</description>
		<content:encoded><![CDATA[<p>Hi Arthur,</p>
<p>Thanks for the correction regarding the cause of the issue - good point. The fault lies with TortoiseSVN rather than the actual protocol.</p>
<p>You&#8217;d think it would be a relatively easy fix, but in the meantime, just Hack It! (TM)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arthur</title>
		<link>http://www.supernifty.com.au/blog/2007/09/27/hack-it-1-change-the-tortoisesvn-ssh-port/#comment-1527</link>
		<dc:creator>Arthur</dc:creator>
		<pubDate>Tue, 05 Aug 2008 13:10:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/?p=16#comment-1527</guid>
		<description>Thanks for this quick fix, it worked out fine for me :)

One thing to point out though;

This is not protocol-related but rather tortoisesvn making an ass out of itself (which otherwise is a fine program).

If it was protocol-related you wouldn't be able to Hack It (TM) in this way and it would also give problems under every other environment, which it doesn't.

I hope they add proper url parsing and / or a port selector soon.

Thanks,
-- Arthur.</description>
		<content:encoded><![CDATA[<p>Thanks for this quick fix, it worked out fine for me <img src='http://www.supernifty.com.au/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>One thing to point out though;</p>
<p>This is not protocol-related but rather tortoisesvn making an ass out of itself (which otherwise is a fine program).</p>
<p>If it was protocol-related you wouldn&#8217;t be able to Hack It (TM) in this way and it would also give problems under every other environment, which it doesn&#8217;t.</p>
<p>I hope they add proper url parsing and / or a port selector soon.</p>
<p>Thanks,<br />
&#8211; Arthur.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
