<?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>Carbonized Blog &#187; spammers</title>
	<atom:link href="http://carbonize.co.uk/wp/tag/spammers/feed/" rel="self" type="application/rss+xml" />
	<link>http://carbonize.co.uk/wp</link>
	<description>Just a bunch of stuff</description>
	<lastBuildDate>Tue, 06 Mar 2012 19:25:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Facebook Wins $711 Million From Spammer</title>
		<link>http://carbonize.co.uk/wp/2009/10/30/facebook-wins-711-million-from-spammer/</link>
		<comments>http://carbonize.co.uk/wp/2009/10/30/facebook-wins-711-million-from-spammer/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 10:29:29 +0000</pubDate>
		<dc:creator>Carbonize</dc:creator>
				<category><![CDATA[Internet]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[spammers]]></category>

		<guid isPermaLink="false">http://carbonize.co.uk/wp/?p=361</guid>
		<description><![CDATA[<a href="http://carbonize.co.uk/wp/2009/10/30/facebook-wins-711-million-from-spammer/" title="Facebook Wins $711 Million From Spammer"></a>Facebook has won a court case against a spammer who was abusing their site to send spam to Facebook users. The spammer known as Spamford, real name Sanford Wallace, is also facing prosecution for criminal contempt of court which could &#8230;<p class="read-more"><a href="http://carbonize.co.uk/wp/2009/10/30/facebook-wins-711-million-from-spammer/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://carbonize.co.uk/wp/2009/10/30/facebook-wins-711-million-from-spammer/" title="Facebook Wins $711 Million From Spammer"></a><p>Facebook has won a court case against a spammer who was abusing their site to send spam to Facebook users. The spammer known as Spamford, real name Sanford Wallace, is also facing prosecution for criminal contempt of court which could result in prison time. Wallace has also previously been prosecuted by MySpace for abusing their site to send porn and MySpace was awarded $230 million.</p>
<p>[<a  href="http://www.guardian.co.uk/media/2009/oct/30/facebook-spam-lawsuit-spamford" target="_blank">source</a>]</p>
]]></content:encoded>
			<wfw:commentRss>http://carbonize.co.uk/wp/2009/10/30/facebook-wins-711-million-from-spammer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blocking IP Addresses Using htaccess</title>
		<link>http://carbonize.co.uk/wp/2009/05/15/blocking-ip-addresses-using-htaccess/</link>
		<comments>http://carbonize.co.uk/wp/2009/05/15/blocking-ip-addresses-using-htaccess/#comments</comments>
		<pubDate>Fri, 15 May 2009 12:26:27 +0000</pubDate>
		<dc:creator>Carbonize</dc:creator>
				<category><![CDATA[spam]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[Script Kiddies]]></category>
		<category><![CDATA[spammers]]></category>

		<guid isPermaLink="false">http://carbonize.co.uk/wp/?p=267</guid>
		<description><![CDATA[<a href="http://carbonize.co.uk/wp/2009/05/15/blocking-ip-addresses-using-htaccess/" title="Blocking IP Addresses Using htaccess"></a>I&#8217;m writing this because blocking by domain on my hosts pretty much kills my web site and so I have had to learn to block ip addresses. Blocking single ip addresses is simple as you just need something like the &#8230;<p class="read-more"><a href="http://carbonize.co.uk/wp/2009/05/15/blocking-ip-addresses-using-htaccess/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://carbonize.co.uk/wp/2009/05/15/blocking-ip-addresses-using-htaccess/" title="Blocking IP Addresses Using htaccess"></a><p>I&#8217;m writing this because blocking by domain on my hosts pretty much kills my web site and so I have had to learn to block ip addresses. Blocking single ip addresses is simple as you just need something like the following</p>
<p> order allow,deny<br />
 deny from 9.120.161.206<br />
 allow from all</p>
<p>And that will block the computer at ip address 9.120.161.206 from being able to access your site. But what if you want to block a whole range of ip addresses such as 9.120.161.0 to 9.120.161.255? Well then we just leave off the end number like this</p>
<p> order allow,deny<br />
 deny from 9.120.161.<br />
 allow from all</p>
<p>Ok so now we get to the clever and damn fiddly bit. As of Apache 1.3 we can use <acronym title="Classless Inter-Domain Routing">CIDR</acronym> codes to specify ranges of ip addresses. So another way of writing the above code would be</p>
<p> order allow,deny<br />
 deny from 9.120.161.0/24<br />
 allow from all</p>
<p>and that would do exactly the same as 9.120.161. but we can do so much more. After the break (ie click the read more link) I will show a list of the CIDR codes and what they do.<br />
<span id="more-267"></span><br />
Ok first thing we need to do is explain that CIDR goes from 0 to 32. 0 covers every possible ip address, all 4,294,967,296 of them so doesn&#8217;t really get used much. As CIDR is based on bits the number of ip addresses blocked doubles as we go down the list.</p>
<p>32 only block the single ip address so is a bit pointless<br />
31 blocks 2 address so would block 127.0.0.1 and 127.0.0.2. Could just as easily be like 127.0.0.19/31 as you can start from any ip address<br />
30 blocks 4 ip address so 127.0.0.1 to 127.0.0.4<br />
29 blocks 8 ip address so 127.0.0.1/29 would block 127.0.0.1 to 127.0.0.8 (starting to see a pattern?)<br />
28 down to 25 I&#8217;m sure you can figure out. It&#8217;s from 24 it gets interesting.<br />
24 blocks a whole sub set of ip addresses (thats 256 addresses) so we can use 127.0.0.0/24 to block 127.0.0.0 to 127.0.0.255<br />
23 blocks 512 address so that&#8217;s 2 entire subsets. 127.0.0.0/23 would block 127.0.0.0 to 127.0.1.255<br />
22 is 1024 addresses or 4 sub sets<br />
21 is 2048 or 8 sub sets<br />
20 is 4096 address or 16 sub sets (like 127.0.0.0 to 127.0.15.255)<br />
19 would be 8192 address so 32 sub sets. I used this one when blocking keyweb.de servers<br />
18 is 16384 or 64 sub sets<br />
17 equals 32768 addresses and I used it to block some layeredtech<br />
16 is the lowest CIDR code I have used and that covers 65536 addresses or 256 sub sets. This is again used to block LayeredTech.</p>
<p>I&#8217;m pretty sure you can work the rest out for yourself from here on. I got my information from <a  href="http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing" target="_blank">this Wikipedia entry</a>. I will now post a couple I have used in my own htaccess and say why.</p>
<p> # These two are for layeredtech. Well known friend to spammers.<br />
 deny from 72.232.0.0/16<br />
 deny from 72.233.0.0/17<br />
 # Keyweb.de servers. Plenty of spam attempts from them<br />
 deny from 87.118.96.0/19<br />
 # Dragonara.net just started getting spam attempts from them<br />
 deny from 194.8.74.0/23</p>
]]></content:encoded>
			<wfw:commentRss>http://carbonize.co.uk/wp/2009/05/15/blocking-ip-addresses-using-htaccess/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

