<?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: Easy password-less SSH login</title>
	<atom:link href="http://techblog.zabuchy.net/2010/simple-password-less-ssh-login/feed/" rel="self" type="application/rss+xml" />
	<link>http://techblog.zabuchy.net/2010/simple-password-less-ssh-login/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=simple-password-less-ssh-login</link>
	<description>GNU/Linux, Open Source and 42</description>
	<lastBuildDate>Tue, 15 May 2012 08:03:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: jimcooncat</title>
		<link>http://techblog.zabuchy.net/2010/simple-password-less-ssh-login/comment-page-1/#comment-52</link>
		<dc:creator>jimcooncat</dc:creator>
		<pubDate>Sun, 06 Jun 2010 13:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.zabuchy.net/?p=120#comment-52</guid>
		<description>If you have multiple users, or if there&#039;s ever the possibility of multiple users on your computer in the future, you need to ensure that this file is not readable by them.

It appears that ssh-keygen does the right thing, allowing only the owner of the file access to it. 

 ls -al .ssh/
will let you verify it. You should see something like:
-rwx------   1 you you   736 2007-05-15 11:26 id_dsa
 or
-rwx------   1 you you   736 2007-05-15 11:26 id_rsa


Where some people get in trouble with sensitive files is with backup schemes. That is, the backups don&#039;t enforce the permissions and others can get access to the file.</description>
		<content:encoded><![CDATA[<p>If you have multiple users, or if there&#8217;s ever the possibility of multiple users on your computer in the future, you need to ensure that this file is not readable by them.</p>
<p>It appears that ssh-keygen does the right thing, allowing only the owner of the file access to it. </p>
<p> ls -al .ssh/<br />
will let you verify it. You should see something like:<br />
-rwx&#8212;&#8212;   1 you you   736 2007-05-15 11:26 id_dsa<br />
 or<br />
-rwx&#8212;&#8212;   1 you you   736 2007-05-15 11:26 id_rsa</p>
<p>Where some people get in trouble with sensitive files is with backup schemes. That is, the backups don&#8217;t enforce the permissions and others can get access to the file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dmitrijs Ledkovs</title>
		<link>http://techblog.zabuchy.net/2010/simple-password-less-ssh-login/comment-page-1/#comment-49</link>
		<dc:creator>Dmitrijs Ledkovs</dc:creator>
		<pubDate>Sat, 05 Jun 2010 02:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://techblog.zabuchy.net/?p=120#comment-49</guid>
		<description>Or install seahorse-plugins, when it asks for the password for the first time click details and tick to unlock when you login.</description>
		<content:encoded><![CDATA[<p>Or install seahorse-plugins, when it asks for the password for the first time click details and tick to unlock when you login.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

