<?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: SSH Known Hosts Fingerprints and Hostnames</title>
	<atom:link href="http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<lastBuildDate>Fri, 17 May 2013 20:46:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta2-24176</generator>
	<item>
		<title>By: cdmiller</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-116487</link>
		<dc:creator>cdmiller</dc:creator>
		<pubDate>Wed, 07 Mar 2012 20:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-116487</guid>
		<description><![CDATA[Thanks. I was looking for the fingerprint of my own machine, now I realize that I can get it with:
ssh-keygen -l -f .ssh/id_rsa.pub]]></description>
		<content:encoded><![CDATA[<p>Thanks. I was looking for the fingerprint of my own machine, now I realize that I can get it with:<br />
ssh-keygen -l -f .ssh/id_rsa.pub</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Links 8/12/2010: Google Linux Announcement, Linux 2.6.37 RC5, PlayStation Phone to Use Linux &#124; Techrights</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111548</link>
		<dc:creator>Links 8/12/2010: Google Linux Announcement, Linux 2.6.37 RC5, PlayStation Phone to Use Linux &#124; Techrights</dc:creator>
		<pubDate>Wed, 08 Dec 2010 13:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111548</guid>
		<description><![CDATA[[...] SSH Known Hosts Fingerprints and Hostnames [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SSH Known Hosts Fingerprints and Hostnames [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111544</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Mon, 06 Dec 2010 01:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111544</guid>
		<description><![CDATA[@Alex- &quot;ssh-keygen -H&#039; already renames the file. The point of removing it, is so you don&#039;t leave anything behind that could compromised.]]></description>
		<content:encoded><![CDATA[<p>@Alex- &#8220;ssh-keygen -H&#8217; already renames the file. The point of removing it, is so you don&#8217;t leave anything behind that could compromised.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111543</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 05 Dec 2010 21:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111543</guid>
		<description><![CDATA[Umm...I&#039;m pretty sure that &quot;ssh-keygen -H &amp;&amp; rm ~/.ssh/known_hosts.old&quot; (taken as a whole) will not have the effect of renaming known_hosts to known_hosts.old.]]></description>
		<content:encoded><![CDATA[<p>Umm&#8230;I&#8217;m pretty sure that &#8220;ssh-keygen -H &amp;&amp; rm ~/.ssh/known_hosts.old&#8221; (taken as a whole) will not have the effect of renaming known_hosts to known_hosts.old.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sven</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111542</link>
		<dc:creator>Sven</dc:creator>
		<pubDate>Sun, 05 Dec 2010 16:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111542</guid>
		<description><![CDATA[Hashing the hostnames in known_hosts has one drawback (at least for me): tab-completion the hostname while using scp, sftp and ssh does no longer work.]]></description>
		<content:encoded><![CDATA[<p>Hashing the hostnames in known_hosts has one drawback (at least for me): tab-completion the hostname while using scp, sftp and ssh does no longer work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111541</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Sun, 05 Dec 2010 15:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111541</guid>
		<description><![CDATA[@Kevin- Very good. Thank you!

@jimcooncat- I was trying to be nice about it, however Fedora-based operating systems should be hashing the hosts, rather than leaving them in plain text. Debian (and as a result Ubuntu) are doing the right thing here. Yes, you could have your home directory with permissions &quot;drwx------&quot; if you wanted, and I understand that thinking, especially on multiuser environments. I prefer the hashing mechanism, especially after learning &quot;ssh-keygen -lf ~/.ssh/known_hosts -F hostname&quot;.]]></description>
		<content:encoded><![CDATA[<p>@Kevin- Very good. Thank you!</p>
<p>@jimcooncat- I was trying to be nice about it, however Fedora-based operating systems should be hashing the hosts, rather than leaving them in plain text. Debian (and as a result Ubuntu) are doing the right thing here. Yes, you could have your home directory with permissions &#8220;drwx&#8212;&#8212;&#8221; if you wanted, and I understand that thinking, especially on multiuser environments. I prefer the hashing mechanism, especially after learning &#8220;ssh-keygen -lf ~/.ssh/known_hosts -F hostname&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimcooncat</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111540</link>
		<dc:creator>jimcooncat</dc:creator>
		<pubDate>Sun, 05 Dec 2010 10:20:43 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111540</guid>
		<description><![CDATA[&quot;It didn’t take long for me to realize that your known_hosts file might be accessible to everyone on the system.&quot;
On my Ubuntu system, permissions for that file are -rw-r--r--

I don&#039;t believe that the ssh package has anything to do with this, but that Ubuntu (and other distros) makes user home directories readable by other users.
http://wwww.ubuntuforums.org/showthread.php?t=1210175

So I&#039;m guessing that because of this *stupid* default, the folks that write ssh decided it was best to hash known_hosts and make it harder to deal with?

It&#039;s simple to pick &quot;encrypted home directories&quot; when installing a system, why shouldn&#039;t it be simple to pick &quot;private home directories&quot;, without encryption?

Just ranting to the world, Aaron. But I hope it sparks more discussion on this issue. Programs shouldn&#039;t have to be made harder to use because distros don&#039;t care about security.]]></description>
		<content:encoded><![CDATA[<p>&#8220;It didn’t take long for me to realize that your known_hosts file might be accessible to everyone on the system.&#8221;<br />
On my Ubuntu system, permissions for that file are -rw-r&#8211;r&#8211;</p>
<p>I don&#8217;t believe that the ssh package has anything to do with this, but that Ubuntu (and other distros) makes user home directories readable by other users.<br />
<a href="http://wwww.ubuntuforums.org/showthread.php?t=1210175" rel="nofollow">http://wwww.ubuntuforums.org/showthread.php?t=1210175</a></p>
<p>So I&#8217;m guessing that because of this *stupid* default, the folks that write ssh decided it was best to hash known_hosts and make it harder to deal with?</p>
<p>It&#8217;s simple to pick &#8220;encrypted home directories&#8221; when installing a system, why shouldn&#8217;t it be simple to pick &#8220;private home directories&#8221;, without encryption?</p>
<p>Just ranting to the world, Aaron. But I hope it sparks more discussion on this issue. Programs shouldn&#8217;t have to be made harder to use because distros don&#8217;t care about security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111539</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Sun, 05 Dec 2010 07:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111539</guid>
		<description><![CDATA[if you do 

ssh-keygen -lf ~/.ssh/known_hosts -F hostname

it will only list ones that match the hostname. This work even when the hostnames are hashed.]]></description>
		<content:encoded><![CDATA[<p>if you do </p>
<p>ssh-keygen -lf ~/.ssh/known_hosts -F hostname</p>
<p>it will only list ones that match the hostname. This work even when the hostnames are hashed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Aaron Toponce : SSH Known Hosts Fingerprints and Hostnames -- Topsy.com</title>
		<link>http://pthree.org/2010/12/04/ssh-known-hosts-fingerprints-and-hostnames/#comment-111538</link>
		<dc:creator>Tweets that mention Aaron Toponce : SSH Known Hosts Fingerprints and Hostnames -- Topsy.com</dc:creator>
		<pubDate>Sun, 05 Dec 2010 06:00:20 +0000</pubDate>
		<guid isPermaLink="false">http://pthree.org/?p=1627#comment-111538</guid>
		<description><![CDATA[[...] This post was mentioned on Twitter by toorghezi, Ubuntu World Wide. Ubuntu World Wide said: #ubuntu #linux Aaron Toponce: SSH Known Hosts Fingerprints and Hostnames: i just came across this today, so I th... http://bit.ly/eBsPDJ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by toorghezi, Ubuntu World Wide. Ubuntu World Wide said: #ubuntu #linux Aaron Toponce: SSH Known Hosts Fingerprints and Hostnames: i just came across this today, so I th&#8230; <a href="http://bit.ly/eBsPDJ" rel="nofollow">http://bit.ly/eBsPDJ</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
