<?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: Brute force password attacks on Linux over SSH</title>
	<atom:link href="http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/</link>
	<description>"I felt a great disturbance in the Force, as if millions of peers suddenly cried out in terror and were suddenly silenced."</description>
	<lastBuildDate>Sun, 22 Oct 2006 16:31:52 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bob</title>
		<link>http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/comment-page-1/#comment-1482</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sat, 02 Sep 2006 16:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/#comment-1482</guid>
		<description>Actually, I use SCP all the time.  Never have a problem with it, but usually tgz all the files prior to transfer.  The SSH protocol may only make the initial connection to port 22 and then transfer to other ports for the additional connections - IIRC that&#039;s the way standard FTP works.</description>
		<content:encoded><![CDATA[<p>Actually, I use SCP all the time.  Never have a problem with it, but usually tgz all the files prior to transfer.  The SSH protocol may only make the initial connection to port 22 and then transfer to other ports for the additional connections &#8211; IIRC that&#8217;s the way standard FTP works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gerry</title>
		<link>http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/comment-page-1/#comment-93</link>
		<dc:creator>gerry</dc:creator>
		<pubDate>Tue, 28 Feb 2006 17:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/#comment-93</guid>
		<description>Interesting...
I take it you don&#039;t use SCP/SFTP often then?

Surely transferring lots of files over SFTP with some clients will cause more than N connections and hence get ya blocked?</description>
		<content:encoded><![CDATA[<p>Interesting&#8230;<br />
I take it you don&#8217;t use SCP/SFTP often then?</p>
<p>Surely transferring lots of files over SFTP with some clients will cause more than N connections and hence get ya blocked?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/comment-page-1/#comment-90</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Sat, 25 Feb 2006 00:00:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/#comment-90</guid>
		<description>Not sure where I found this, but I added these rules to my iptables configuration.  It limits the number of access attempts to an ssh port.  If an ip address connects more than 3 times they are locked out for 600 seconds.  Mostly eliminated hacker attacks on my ssh port.

# rate-limit ssh traffic

 iptables -I INPUT -p tcp --dport 22 -i eth1 -m state --state NEW -m recent --set

iptables -I INPUT -p tcp --dport 22 -i eth1 -m state --state NEW -m recent --update --seconds 600 --hitcount 4 -j DROP</description>
		<content:encoded><![CDATA[<p>Not sure where I found this, but I added these rules to my iptables configuration.  It limits the number of access attempts to an ssh port.  If an ip address connects more than 3 times they are locked out for 600 seconds.  Mostly eliminated hacker attacks on my ssh port.</p>
<p># rate-limit ssh traffic</p>
<p> iptables -I INPUT -p tcp &#8211;dport 22 -i eth1 -m state &#8211;state NEW -m recent &#8211;set</p>
<p>iptables -I INPUT -p tcp &#8211;dport 22 -i eth1 -m state &#8211;state NEW -m recent &#8211;update &#8211;seconds 600 &#8211;hitcount 4 -j DROP</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Of Shite</title>
		<link>http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/comment-page-1/#comment-79</link>
		<dc:creator>Web Of Shite</dc:creator>
		<pubDate>Thu, 09 Feb 2006 02:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lobstertechnology.com/2006/02/08/brute-force-passwords-attacks-on-linux-over-ssh/#comment-79</guid>
		<description>&lt;strong&gt;SSHD Filter&lt;/strong&gt;

	sshdfilter helps protect against bruteforce attacks.

...</description>
		<content:encoded><![CDATA[<p><strong>SSHD Filter</strong></p>
<p>	sshdfilter helps protect against bruteforce attacks.</p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
