<?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: setting up RSync over SSH with No Password</title>
	<atom:link href="http://www.paulmellors.net/2008/02/29/setting-up-rsync-over-ssh-with-no-password/feed" rel="self" type="application/rss+xml" />
	<link>http://www.paulmellors.net/2008/02/29/setting-up-rsync-over-ssh-with-no-password</link>
	<description>Trial and Tribulations of a Windows / Linux User</description>
	<pubDate>Sat, 22 Nov 2008 06:07:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3-9771</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Neil Greenwood</title>
		<link>http://www.paulmellors.net/2008/02/29/setting-up-rsync-over-ssh-with-no-password/comment-page-1#comment-350</link>
		<dc:creator>Neil Greenwood</dc:creator>
		<pubDate>Tue, 11 Mar 2008 15:47:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulmellors.net/2008/02/29/setting-up-rsync-over-ssh-with-no-password#comment-350</guid>
		<description>Step 2 can be simplified by using the ssh-copy-id command.</description>
		<content:encoded><![CDATA[<p>Step 2 can be simplified by using the ssh-copy-id command.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laney</title>
		<link>http://www.paulmellors.net/2008/02/29/setting-up-rsync-over-ssh-with-no-password/comment-page-1#comment-329</link>
		<dc:creator>Laney</dc:creator>
		<pubDate>Sat, 01 Mar 2008 19:02:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulmellors.net/2008/02/29/setting-up-rsync-over-ssh-with-no-password#comment-329</guid>
		<description>Of course this is terribly insecure, allowing full shell access without a password. Fortunately there is a way to mitigate this somewhat by prefixing the public key in your authorized_keys file to restrict a particular key to only running certain commands. Here's mine:

command="/home/laney/.ssh/check_command",from="my.i.p",no-port-forwarding,no-X11-forwarding,no-pty  

Which validates the command (ssh user@host ), restricts to a single IP, and disables port forwarding and many other things. Much more secure, although obviously only as secure as those commands which you allow.

check_command is here: http://orangesquash.org.uk/~laney/check_command</description>
		<content:encoded><![CDATA[<p>Of course this is terribly insecure, allowing full shell access without a password. Fortunately there is a way to mitigate this somewhat by prefixing the public key in your authorized_keys file to restrict a particular key to only running certain commands. Here&#8217;s mine:</p>
<p>command=&#8221;/home/laney/.ssh/check_command&#8221;,from=&#8221;my.i.p&#8221;,no-port-forwarding,no-X11-forwarding,no-pty  </p>
<p>Which validates the command (ssh user@host ), restricts to a single IP, and disables port forwarding and many other things. Much more secure, although obviously only as secure as those commands which you allow.</p>
<p>check_command is here: <a href="http://orangesquash.org.uk/~laney/check_command" rel="nofollow">http://orangesquash.org.uk/~laney/check_command</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
