<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: svn+ssh</title>
	<atom:link href="http://blog.bodhizazen.net/linux/svnssh/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bodhizazen.net/linux/svnssh/</link>
	<description>A LAMP in the Samsara</description>
	<lastBuildDate>Tue, 31 Jan 2012 20:20:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: bodhi.zazen</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-3983</link>
		<dc:creator>bodhi.zazen</dc:creator>
		<pubDate>Thu, 21 Jul 2011 22:25:46 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-3983</guid>
		<description>@shankao - thanks for the information, it is a somewhat old blog, so your update is helpful.

I have found, using the default port is easier for clients who are new to the protocols, changing the port has security advantages, but is inconvenient for clients.

As it is ssh , I use keys, and disable passwords, and leave the ssh server running on port 22. Adding apparmor or selinux (rather then changing the port) would be the next step, IMO.</description>
		<content:encoded><![CDATA[<p>@shankao &#8211; thanks for the information, it is a somewhat old blog, so your update is helpful.</p>
<p>I have found, using the default port is easier for clients who are new to the protocols, changing the port has security advantages, but is inconvenient for clients.</p>
<p>As it is ssh , I use keys, and disable passwords, and leave the ssh server running on port 22. Adding apparmor or selinux (rather then changing the port) would be the next step, IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shankao</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-3980</link>
		<dc:creator>shankao</dc:creator>
		<pubDate>Thu, 21 Jul 2011 04:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-3980</guid>
		<description>The port specification does not work with my current svn version (1.6.11)

The only way I have found is by changing the ssh protocol scheme in the config&#039;s file &quot;tunnels&quot; section. Something like this:

ssh = $SVN_SSH ssh -q -p 27012

...but that has effect for every host :-/</description>
		<content:encoded><![CDATA[<p>The port specification does not work with my current svn version (1.6.11)</p>
<p>The only way I have found is by changing the ssh protocol scheme in the config&#8217;s file &#8220;tunnels&#8221; section. Something like this:</p>
<p>ssh = $SVN_SSH ssh -q -p 27012</p>
<p>&#8230;but that has effect for every host :-/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shared SSH Sessions &#171; System admin made easy</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-3909</link>
		<dc:creator>Shared SSH Sessions &#171; System admin made easy</dc:creator>
		<pubDate>Sat, 02 Jul 2011 13:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-3909</guid>
		<description>[...] If you do not understand this, see my blog on svn+ssh. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you do not understand this, see my blog on svn+ssh. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 1</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-1335</link>
		<dc:creator>1</dc:creator>
		<pubDate>Tue, 01 Dec 2009 08:10:02 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-1335</guid>
		<description>I would write :
“svn checkout svn+ssh://user@host:8822/”
I not have the time to test :(, but if it works for the host.
My point is that by this way you may not have to configure the client. It&#039;s always a good point ;)</description>
		<content:encoded><![CDATA[<p>I would write :<br />
“svn checkout svn+ssh://user@host:8822/”<br />
I not have the time to test :(, but if it works for the host.<br />
My point is that by this way you may not have to configure the client. It&#8217;s always a good point ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bodhi.zazen</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-1332</link>
		<dc:creator>bodhi.zazen</dc:creator>
		<pubDate>Mon, 30 Nov 2009 19:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-1332</guid>
		<description>Your command did not specify any options. You did not specify a port for example.

You can not (or at least at the time I wrote the tutorial) :

&quot;svn -p 8822 checkout svn+ssh://user@host/&quot;</description>
		<content:encoded><![CDATA[<p>Your command did not specify any options. You did not specify a port for example.</p>
<p>You can not (or at least at the time I wrote the tutorial) :</p>
<p>&#8220;svn -p 8822 checkout svn+ssh://user@host/&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 1</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-1331</link>
		<dc:creator>1</dc:creator>
		<pubDate>Mon, 30 Nov 2009 11:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-1331</guid>
		<description>Hello,

Thanks for the tips. But I don&#039;t understand :
[...] svn+ssh will not take options for log in user or port, so we must edit ~/.subversion [...]

&quot;svn checkout svn+ssh://user@host/&quot; works for me... What is the difference ?</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Thanks for the tips. But I don&#8217;t understand :<br />
[...] svn+ssh will not take options for log in user or port, so we must edit ~/.subversion [...]</p>
<p>&#8220;svn checkout svn+ssh://user@host/&#8221; works for me&#8230; What is the difference ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bodhi.zazen</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-1272</link>
		<dc:creator>bodhi.zazen</dc:creator>
		<pubDate>Mon, 16 Nov 2009 05:53:31 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-1272</guid>
		<description>Dale: I have no experience with Tortoise SVN, but looking on the home page :

http://tortoisesvn.tigris.org/

They claim &quot;All Subversion protocols are supported&quot;, and they list svn+ssh

So my guess would be you will be fine. Set up the SVN server as above, and configure your Tortoise client to use svn+ssh .

See: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-ssh-howto.html</description>
		<content:encoded><![CDATA[<p>Dale: I have no experience with Tortoise SVN, but looking on the home page :</p>
<p><a href="http://tortoisesvn.tigris.org/" rel="nofollow">http://tortoisesvn.tigris.org/</a></p>
<p>They claim &#8220;All Subversion protocols are supported&#8221;, and they list svn+ssh</p>
<p>So my guess would be you will be fine. Set up the SVN server as above, and configure your Tortoise client to use svn+ssh .</p>
<p>See: <a href="http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-ssh-howto.html" rel="nofollow">http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-ssh-howto.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-1270</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Sun, 15 Nov 2009 17:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-1270</guid>
		<description>Bodhi, can this approach be used with Tortoise SVN from a Windows client?  If so, any pointers for such configuration?  I&#039;ve tried a number of things, but can&#039;t get past a login on the server.</description>
		<content:encoded><![CDATA[<p>Bodhi, can this approach be used with Tortoise SVN from a Windows client?  If so, any pointers for such configuration?  I&#8217;ve tried a number of things, but can&#8217;t get past a login on the server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bodhi.zazen</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-521</link>
		<dc:creator>bodhi.zazen</dc:creator>
		<pubDate>Sun, 29 Mar 2009 04:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-521</guid>
		<description>Thank you Andrew Canuck for pointing out those &quot;small points&quot;, your feedback is greatly appreciated.

My post has been updated.</description>
		<content:encoded><![CDATA[<p>Thank you Andrew Canuck for pointing out those &#8220;small points&#8221;, your feedback is greatly appreciated.</p>
<p>My post has been updated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shadows of epiphany &#187; Blog Archive &#187; Shared SSH Sessions, Update for Jaunty (Ubuntu 9.04)</title>
		<link>http://blog.bodhizazen.net/linux/svnssh/comment-page-1/#comment-514</link>
		<dc:creator>Shadows of epiphany &#187; Blog Archive &#187; Shared SSH Sessions, Update for Jaunty (Ubuntu 9.04)</dc:creator>
		<pubDate>Sat, 28 Mar 2009 06:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://bodhizazen.net/bzblog/?p=5#comment-514</guid>
		<description>[...] If you do not understand this, see my blog on svn+ssh. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you do not understand this, see my blog on svn+ssh. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

