<?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: How to fix your hackable SSH on Debian and Ubuntu Servers</title>
	<atom:link href="http://www.mattgibson.ca/2008/05/15/how-to-fix-your-hackable-ssh-on-debian-and-ubuntu-servers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mattgibson.ca/2008/05/15/how-to-fix-your-hackable-ssh-on-debian-and-ubuntu-servers/</link>
	<description>I'm one of those people radio shows call for obscure shit.</description>
	<lastBuildDate>Tue, 31 Aug 2010 07:35:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Christopher DeMarco</title>
		<link>http://www.mattgibson.ca/2008/05/15/how-to-fix-your-hackable-ssh-on-debian-and-ubuntu-servers/comment-page-1/#comment-771</link>
		<dc:creator>Christopher DeMarco</dc:creator>
		<pubDate>Thu, 15 May 2008 20:11:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mattgibson.ca/archives/107#comment-771</guid>
		<description>This only fixes connections from this host to others.  Inbound connections are still problematic!

You need to edit your /etc/ssh/sshd_config file, and set these options: 

    RSAAuthentication no
    PubkeyAuthenticatio no

Then remove the .ssh/authorized_keys and authorized_keys2 files in EVERY USER&#039;s HOME DIRECTORY.  (cut -d: -f6 &lt; /etc/passwd) .

After that, you can flip those sshd_config options back on.  

NOW you&#039;re safe!</description>
		<content:encoded><![CDATA[<p>This only fixes connections from this host to others.  Inbound connections are still problematic!</p>
<p>You need to edit your /etc/ssh/sshd_config file, and set these options: </p>
<p>    RSAAuthentication no<br />
    PubkeyAuthenticatio no</p>
<p>Then remove the .ssh/authorized_keys and authorized_keys2 files in EVERY USER&#8217;s HOME DIRECTORY.  (cut -d: -f6 &lt; /etc/passwd) .</p>
<p>After that, you can flip those sshd_config options back on.  </p>
<p>NOW you&#8217;re safe!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
