<?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: Protecting against SSH brute-force password attacks</title>
	<atom:link href="http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 22:52:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Hagopian</title>
		<link>http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/comment-page-1/#comment-1209</link>
		<dc:creator>Rob Hagopian</dc:creator>
		<pubDate>Mon, 08 Dec 2008 19:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/#comment-1209</guid>
		<description>Longer passwords are more difficult to crack than adding a little more complexity via special characters. For instance:

Mary had a little lamb

is a much stronger password than

Mary12$

-Rob</description>
		<content:encoded><![CDATA[<p>Longer passwords are more difficult to crack than adding a little more complexity via special characters. For instance:</p>
<p>Mary had a little lamb</p>
<p>is a much stronger password than</p>
<p>Mary12$</p>
<p>-Rob</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LKRaider</title>
		<link>http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/comment-page-1/#comment-606</link>
		<dc:creator>LKRaider</dc:creator>
		<pubDate>Sat, 27 Sep 2008 18:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/#comment-606</guid>
		<description>Thanks, that's exactly what I needed! :)</description>
		<content:encoded><![CDATA[<p>Thanks, that&#8217;s exactly what I needed! <img src='http://www.steveglendinning.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/comment-page-1/#comment-582</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 25 Sep 2008 09:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/#comment-582</guid>
		<description>Hi LKRaider,

Yes, but only if you have OpenSSH 4.3p2 or later.  You can use the new "Match" configuration block to override some settings for selected hosts, users or groups.

There's an example of using it here: &lt;a href="http://prefetch.net/blog/index.php/2006/09/05/limiting-access-to-openssh-directives/" rel="nofollow"&gt;http://prefetch.net/blog/index.php/2006/09/05/limiting-access-to-openssh-directives/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Hi LKRaider,</p>
<p>Yes, but only if you have OpenSSH 4.3p2 or later.  You can use the new &#8220;Match&#8221; configuration block to override some settings for selected hosts, users or groups.</p>
<p>There&#8217;s an example of using it here: <a href="http://prefetch.net/blog/index.php/2006/09/05/limiting-access-to-openssh-directives/" rel="nofollow">http://prefetch.net/blog/index.php/2006/09/05/limiting-access-to-openssh-directives/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LKRaider</title>
		<link>http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/comment-page-1/#comment-580</link>
		<dc:creator>LKRaider</dc:creator>
		<pubDate>Wed, 24 Sep 2008 05:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.steveglendinning.com/2008/01/27/protecting-against-ssh-brute-force-password-attacks/#comment-580</guid>
		<description>Hello,

Is it possible to enable Password Authentication for a specified host only, while keeping Pubkey Authentication for any other hosts available?

I ask this because I currently use public key authentication, but want to setup freenx on the host, and using sshd to control the login is by far the easiest method to setup (no need to recreate passwords for passdb, for instance), but requires password authentication enabled on localhost to work.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Is it possible to enable Password Authentication for a specified host only, while keeping Pubkey Authentication for any other hosts available?</p>
<p>I ask this because I currently use public key authentication, but want to setup freenx on the host, and using sshd to control the login is by far the easiest method to setup (no need to recreate passwords for passdb, for instance), but requires password authentication enabled on localhost to work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
