<?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: Gettin&#8217; hacked</title>
	<atom:link href="http://www.guru.net.nz/blog/2008/09/gettin-hacked.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.guru.net.nz/blog/2008/09/gettin-hacked.html</link>
	<description>Random stuff from a Dunedin (NZ) based web developer, beer drinker and dad</description>
	<lastBuildDate>Mon, 30 Aug 2010 22:42:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: oz</title>
		<link>http://www.guru.net.nz/blog/2008/09/gettin-hacked.html#comment-489</link>
		<dc:creator>oz</dc:creator>
		<pubDate>Fri, 09 Jan 2009 11:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.guru.net.nz/newblog/?p=187#comment-489</guid>
		<description>fail2ban worked good as gold for me, but yeah you need iptables/ipchains running
blocks malformed apache attacks too</description>
		<content:encoded><![CDATA[<p>fail2ban worked good as gold for me, but yeah you need iptables/ipchains running<br />
blocks malformed apache attacks too</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan</title>
		<link>http://www.guru.net.nz/blog/2008/09/gettin-hacked.html#comment-305</link>
		<dc:creator>Nathan</dc:creator>
		<pubDate>Thu, 02 Oct 2008 01:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.guru.net.nz/newblog/?p=187#comment-305</guid>
		<description>In regards to the SSH attempts, you could always try running the SSH daemon on a custom port.&lt;br/&gt;&lt;br/&gt;I used to have heaps of login attempts, and changing the port to something else has eliminated these completely.</description>
		<content:encoded><![CDATA[<p>In regards to the SSH attempts, you could always try running the SSH daemon on a custom port.</p>
<p>I used to have heaps of login attempts, and changing the port to something else has eliminated these completely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guru</title>
		<link>http://www.guru.net.nz/blog/2008/09/gettin-hacked.html#comment-304</link>
		<dc:creator>Guru</dc:creator>
		<pubDate>Sat, 27 Sep 2008 12:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.guru.net.nz/newblog/?p=187#comment-304</guid>
		<description>I think I&#039;ve found and fixed the problem.  The SSH hacking was coincidental and resulted in me finding out a bit more about fail2ban (will have to run ipchains alongside it I think - not currently doing that).&lt;br/&gt;&lt;br/&gt;The bandwidth was eaten up because someone sent me a 16MB email, and my custom delivery solution (home made, probably already exists as part of exim) was choking because the PHP CLI was configured to allow a maximum script size of 32MB.  I bumped it up to 64MB and the email came through.  I guess my script is holding a copy of the whole message in memory or something (it does some mail header parsing).&lt;br/&gt;&lt;br/&gt;So, it had been trying to download it pretty much constantly for the last three days and failing, then trying again.  The bugger about this is that as far as my ISP is concerned this will be chargable bandwidth $#*#@!&lt;br/&gt;&lt;br/&gt;Who sends images as BMP&#039;s anyway?!&lt;br/&gt;&lt;br/&gt;Will keep an eye on it but I think it&#039;s fixed.</description>
		<content:encoded><![CDATA[<p>I think I&#8217;ve found and fixed the problem.  The SSH hacking was coincidental and resulted in me finding out a bit more about fail2ban (will have to run ipchains alongside it I think &#8211; not currently doing that).</p>
<p>The bandwidth was eaten up because someone sent me a 16MB email, and my custom delivery solution (home made, probably already exists as part of exim) was choking because the PHP CLI was configured to allow a maximum script size of 32MB.  I bumped it up to 64MB and the email came through.  I guess my script is holding a copy of the whole message in memory or something (it does some mail header parsing).</p>
<p>So, it had been trying to download it pretty much constantly for the last three days and failing, then trying again.  The bugger about this is that as far as my ISP is concerned this will be chargable bandwidth $#*#@!</p>
<p>Who sends images as BMP&#8217;s anyway?!</p>
<p>Will keep an eye on it but I think it&#8217;s fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guru</title>
		<link>http://www.guru.net.nz/blog/2008/09/gettin-hacked.html#comment-303</link>
		<dc:creator>Guru</dc:creator>
		<pubDate>Sat, 27 Sep 2008 06:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.guru.net.nz/newblog/?p=187#comment-303</guid>
		<description>I&#039;m suspecting something else as well - you&#039;re right, SSH shouldn&#039;t use that much, unless there&#039;s some kind of weird attack under way that isn&#039;t resulting in actual SSH failed login attempts.&lt;br/&gt;&lt;br/&gt;I&#039;ve hopefully got a quiet evening at home alone tonight (baby sleep willing) so will have to look closer.  Have had another gig eaten up since lunchtime (~6 hours).&lt;br/&gt;&lt;br/&gt;Will have to look at some kind of application bandwidth reporting as well for future interest.  Would have been nice to get on top of this sooner.</description>
		<content:encoded><![CDATA[<p>I&#8217;m suspecting something else as well &#8211; you&#8217;re right, SSH shouldn&#8217;t use that much, unless there&#8217;s some kind of weird attack under way that isn&#8217;t resulting in actual SSH failed login attempts.</p>
<p>I&#8217;ve hopefully got a quiet evening at home alone tonight (baby sleep willing) so will have to look closer.  Have had another gig eaten up since lunchtime (~6 hours).</p>
<p>Will have to look at some kind of application bandwidth reporting as well for future interest.  Would have been nice to get on top of this sooner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.guru.net.nz/blog/2008/09/gettin-hacked.html#comment-302</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 27 Sep 2008 03:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.guru.net.nz/newblog/?p=187#comment-302</guid>
		<description>I thought by default fail2ban would ban after 4 failed attempts for 10 minutes.  You could try setting some iptable rules yourself. Seems crazy that ssh login attempts used that much bandwidth.</description>
		<content:encoded><![CDATA[<p>I thought by default fail2ban would ban after 4 failed attempts for 10 minutes.  You could try setting some iptable rules yourself. Seems crazy that ssh login attempts used that much bandwidth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
