<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>FewBar.com - Make it good &#187; collaboration</title>
	<atom:link href="http://fewbar.com/tag/collaboration/feed/" rel="self" type="application/rss+xml" />
	<link>http://fewbar.com</link>
	<description>Technology, life, and mischief, not in that order</description>
	<lastBuildDate>Wed, 18 Apr 2012 00:55:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>SSH brute force protection &#8211; Its almost always already written</title>
		<link>http://fewbar.com/2009/08/ssh-brute-force-protection-its-almost-always-already-written/</link>
		<comments>http://fewbar.com/2009/08/ssh-brute-force-protection-its-almost-always-already-written/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 16:49:36 +0000</pubDate>
		<dc:creator>clint</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[collaboration]]></category>
		<category><![CDATA[opensource]]></category>
		<category><![CDATA[python]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://fewbar.com/?p=111</guid>
		<description><![CDATA[<a href="http://fewbar.com/2009/08/ssh-brute-force-protection-its-almost-always-already-written/" title="SSH brute force protection - Its almost always already written"></a>Every time I get my logwatch report and see the 20 &#8211; 40 daily brute force attempts on it, I cringe. I&#8217;ve locked it down to a point, but ultimately I prefer convenience on some level. Limiting any one IP &#8230;<p class="read-more"><a href="http://fewbar.com/2009/08/ssh-brute-force-protection-its-almost-always-already-written/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://fewbar.com/2009/08/ssh-brute-force-protection-its-almost-always-already-written/" title="SSH brute force protection - Its almost always already written"></a><p>Every time I get my logwatch report and see the 20 &#8211; 40 daily brute force attempts on it, I cringe. I&#8217;ve locked it down to a point, but ultimately I prefer convenience on some level. Limiting any one IP to 2 ssh connections every 5 minutes has annoyed me as many times as it has probably saved me. Preventing root from logging in is nice too.</p>
<p>Ultimately though, I wanted a way to fight back against the brute forcers.. to get a step ahead of them. From seeing the success of projects like <a href="http://spamhaus.org">SpamHAUS</a> and <a href="http://www.projecthoneypot.org">Project HoneyPot</a>, I know that massive group collaboration works. Of course I started thinking how I&#8217;d write it in my head. Every time&#8230; for months.</p>
<p>Well, once I let go of my egotistical desire to write it, I found this great project, <a href="http://denyhosts.sourceforge.net">DenyHosts</a>, which does the same thing for the brute force scanners. I just installed it, and already it has added a few IPs to hosts.deny. Go download it, run it, and stop the annoying scanners!</p>
]]></content:encoded>
			<wfw:commentRss>http://fewbar.com/2009/08/ssh-brute-force-protection-its-almost-always-already-written/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.154 seconds -->

