<?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: SIP Attacks From Amazon EC2 Cloud Continue</title>
	<atom:link href="http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/</link>
	<description>Patrick and Fred Chat... sometimes about VoIP</description>
	<lastBuildDate>Thu, 26 Jan 2012 19:23:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dan</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-3343</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 18 Nov 2010 15:40:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-3343</guid>
		<description>BTW ... check out http://www.infiltrated.net/voipabuse/submitting-info.html</description>
		<content:encoded><![CDATA[<p>BTW &#8230; check out <a href="http://www.infiltrated.net/voipabuse/submitting-info.html" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/www.infiltrated.net/voipabuse/submitting-info.html?referer=');">http://www.infiltrated.net/voipabuse/submitting-info.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-3342</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 18 Nov 2010 15:15:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-3342</guid>
		<description>As a VoIP service provider, we find most attacks currently coming from China. On top of the router blocking suggested above, we install &quot;fail2ban&quot; and configure it to 5 attempts and the IP address is blocked.  

It helps, but the real answer is for ISPs to be notified and them being responsible enough to shut down the attackers.

The question is how do we get ISPs, even Amazon, to listen and act?</description>
		<content:encoded><![CDATA[<p>As a VoIP service provider, we find most attacks currently coming from China. On top of the router blocking suggested above, we install &#8220;fail2ban&#8221; and configure it to 5 attempts and the IP address is blocked.  </p>
<p>It helps, but the real answer is for ISPs to be notified and them being responsible enough to shut down the attackers.</p>
<p>The question is how do we get ISPs, even Amazon, to listen and act?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I&#8217;ll have clear skies, personal conversation, and hold the technology, please. &#124; VoIP Tech Chat</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-3246</link>
		<dc:creator>I&#8217;ll have clear skies, personal conversation, and hold the technology, please. &#124; VoIP Tech Chat</dc:creator>
		<pubDate>Fri, 08 Oct 2010 15:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-3246</guid>
		<description>[...] Apologies to Fred for shout-outs to two of his nemeses, Amazon and [...]</description>
		<content:encoded><![CDATA[<p>[...] Apologies to Fred for shout-outs to two of his nemeses, Amazon and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brent</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-2821</link>
		<dc:creator>brent</dc:creator>
		<pubDate>Fri, 27 Aug 2010 20:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-2821</guid>
		<description>Hopefully the IP restrictions and lawsuits will send the right message.

For the moment, it appears that, Mr. Bezos&#039; loyalty rests with paying AWS customers (aka attackers) and not the victims of abuse.</description>
		<content:encoded><![CDATA[<p>Hopefully the IP restrictions and lawsuits will send the right message.</p>
<p>For the moment, it appears that, Mr. Bezos&#8217; loyalty rests with paying AWS customers (aka attackers) and not the victims of abuse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: UxBoD</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-2515</link>
		<dc:creator>UxBoD</dc:creator>
		<pubDate>Mon, 24 May 2010 11:52:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-2515</guid>
		<description>My system as just been attacked again. Sent the details to AmazonWS and their response was:

&quot;Thank you for submitting your abuse report.
There was no single customer using the source IP address(es) during the time you provided.
This may be due to the fact that we do not own the IP address(es), the time or time zone you provided was incorrect, or there were multiple customers with instances running during the time and IP address(es) you specified.
You may try re-submitting your report with a different time if you wish.&quot;

Uh, sorry but it was one of your servers!

dig +short -x 204.236.207.65
ec2-204-236-207-65.compute-1.amazonaws.com.</description>
		<content:encoded><![CDATA[<p>My system as just been attacked again. Sent the details to AmazonWS and their response was:</p>
<p>&#8220;Thank you for submitting your abuse report.<br />
There was no single customer using the source IP address(es) during the time you provided.<br />
This may be due to the fact that we do not own the IP address(es), the time or time zone you provided was incorrect, or there were multiple customers with instances running during the time and IP address(es) you specified.<br />
You may try re-submitting your report with a different time if you wish.&#8221;</p>
<p>Uh, sorry but it was one of your servers!</p>
<p>dig +short -x 204.236.207.65<br />
ec2-204-236-207-65.compute-1.amazonaws.com.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-2504</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Sat, 22 May 2010 01:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-2504</guid>
		<description>Time to start blocking these IP ranges at the boarder of your networks. As an ITSP / ISP I have the luxury of beefy routers and firewalls, however the loan PBX at the customer prem is in trouble. Even with firewall rules in place odds are the little routers will simply fail under the load of traffic coming from EC2. 

Time for people to start complaining to there ISP&#039;s and let us start contacting Amazon and blocking the attacks upstream before they reach your PBX&#039;s.

For reference, Current amazon EC2 IP ranges.

US East (Northern Virginia):
216.182.224.0/20 (216.182.224.0 – 216.182.239.255)
72.44.32.0/19 (72.44.32.0 – 72.44.63.255)
67.202.0.0/18 (67.202.0.0 – 67.202.63.255)
75.101.128.0/17 (75.101.128.0 – 75.101.255.255)
174.129.0.0/16 (174.129.0.0 – 174.129.255.255)
204.236.192.0/18 (204.236.192.0 – 204.236.255.255)
184.73.0.0/16 (184.73.0.0 – 184.73.255.255)
184.72.128.0/17 (184.72.128.0 – 184.72.255.255)

US West (Northern California):
204.236.128.0/18 (216.236.128.0 – 216.236.191.255)
184.72.0.0/18 (184.72.0.0 – 184.72.63.255)

EU (Ireland):
79.125.0.0/17 (79.125.0.0 – 79.125.127.255)

Asia Pacific (Singapore)
175.41.128.0/18 (175.41.128.0 – 175.41.191.255)</description>
		<content:encoded><![CDATA[<p>Time to start blocking these IP ranges at the boarder of your networks. As an ITSP / ISP I have the luxury of beefy routers and firewalls, however the loan PBX at the customer prem is in trouble. Even with firewall rules in place odds are the little routers will simply fail under the load of traffic coming from EC2. </p>
<p>Time for people to start complaining to there ISP&#8217;s and let us start contacting Amazon and blocking the attacks upstream before they reach your PBX&#8217;s.</p>
<p>For reference, Current amazon EC2 IP ranges.</p>
<p>US East (Northern Virginia):<br />
216.182.224.0/20 (216.182.224.0 – 216.182.239.255)<br />
72.44.32.0/19 (72.44.32.0 – 72.44.63.255)<br />
67.202.0.0/18 (67.202.0.0 – 67.202.63.255)<br />
75.101.128.0/17 (75.101.128.0 – 75.101.255.255)<br />
174.129.0.0/16 (174.129.0.0 – 174.129.255.255)<br />
204.236.192.0/18 (204.236.192.0 – 204.236.255.255)<br />
184.73.0.0/16 (184.73.0.0 – 184.73.255.255)<br />
184.72.128.0/17 (184.72.128.0 – 184.72.255.255)</p>
<p>US West (Northern California):<br />
204.236.128.0/18 (216.236.128.0 – 216.236.191.255)<br />
184.72.0.0/18 (184.72.0.0 – 184.72.63.255)</p>
<p>EU (Ireland):<br />
79.125.0.0/17 (79.125.0.0 – 79.125.127.255)</p>
<p>Asia Pacific (Singapore)<br />
175.41.128.0/18 (175.41.128.0 – 175.41.191.255)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garrett Smith - VoIP</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-2689</link>
		<dc:creator>Garrett Smith - VoIP</dc:creator>
		<pubDate>Mon, 17 May 2010 19:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-2689</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @teamforrest: Using #asterisk? Check out our script http://bit.ly/cDHlLq to help prevent Amazon EC2 SIP attacks http://bit.ly/ec2sipflood&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @teamforrest: Using #asterisk? Check out our script <a href="http://bit.ly/cDHlLq" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/bit.ly/cDHlLq?referer=');">http://bit.ly/cDHlLq</a> to help prevent Amazon EC2 SIP attacks <a href="http://bit.ly/ec2sipflood" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/bit.ly/ec2sipflood?referer=');">http://bit.ly/ec2sipflood</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David A. Bryan</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-2690</link>
		<dc:creator>David A. Bryan</dc:creator>
		<pubDate>Mon, 17 May 2010 17:05:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-2690</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @DaveMichels: [Sharing..] SIP Attacks From Amazon EC2 Cloud Continue: Attacks from the cloud. Just over a… http://goo.gl/fb/hlFW4&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @DaveMichels: [Sharing..] SIP Attacks From Amazon EC2 Cloud Continue: Attacks from the cloud. Just over a… <a href="http://goo.gl/fb/hlFW4" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/goo.gl/fb/hlFW4?referer=');">http://goo.gl/fb/hlFW4</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David A. Bryan</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-2691</link>
		<dc:creator>David A. Bryan</dc:creator>
		<pubDate>Mon, 17 May 2010 17:04:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-2691</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;TY @DaveMichels: SIP Attacks From Amazon EC2 Cloud Continue: Attacks from the cloud. http://goo.gl/fb/hlFW4&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">TY @DaveMichels: SIP Attacks From Amazon EC2 Cloud Continue: Attacks from the cloud. <a href="http://goo.gl/fb/hlFW4" rel="nofollow" onclick="pageTracker._trackPageview('/outgoing/goo.gl/fb/hlFW4?referer=');">http://goo.gl/fb/hlFW4</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Attacking VOIP From the Cloud &#8211; Upland Strategy Group, LLC</title>
		<link>http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/comment-page-1/#comment-2439</link>
		<dc:creator>Attacking VOIP From the Cloud &#8211; Upland Strategy Group, LLC</dc:creator>
		<pubDate>Mon, 17 May 2010 15:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.voiptechchat.com/?p=538#comment-2439</guid>
		<description>[...] http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/" rel="nofollow">http://www.voiptechchat.com/voip/538/sip-attacks-from-amazon-ec2-cloud-continue/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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

