<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Something fishy about all of this&#8230;</title>
	<atom:link href="http://warbrain.wordpress.com/2007/11/20/something-fishy-about-all-of-this/feed/" rel="self" type="application/rss+xml" />
	<link>http://warbrain.wordpress.com/2007/11/20/something-fishy-about-all-of-this/</link>
	<description>Like tech?  Like Apple?  So do I.</description>
	<lastBuildDate>Tue, 02 Sep 2008 13:47:36 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matt</title>
		<link>http://warbrain.wordpress.com/2007/11/20/something-fishy-about-all-of-this/#comment-946</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 28 Nov 2007 02:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://warbrain.wordpress.com/2007/11/20/something-fishy-about-all-of-this/#comment-946</guid>
		<description>As someone who runs numerous high profile sites, really everyone either runs through another compromised server, or somewhere out of the netherlands (go figure). I&#039;ve tried getting some of the other compromised machines shut down and I never hear back from the abuse departments of those netblocks. Any more I don&#039;t even bother.</description>
		<content:encoded><![CDATA[<p>As someone who runs numerous high profile sites, really everyone either runs through another compromised server, or somewhere out of the netherlands (go figure). I&#8217;ve tried getting some of the other compromised machines shut down and I never hear back from the abuse departments of those netblocks. Any more I don&#8217;t even bother.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nfreader</title>
		<link>http://warbrain.wordpress.com/2007/11/20/something-fishy-about-all-of-this/#comment-945</link>
		<dc:creator>nfreader</dc:creator>
		<pubDate>Wed, 21 Nov 2007 03:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://warbrain.wordpress.com/2007/11/20/something-fishy-about-all-of-this/#comment-945</guid>
		<description>I hate to break it to you but I think you&#039;re wrong. None of this is staged. 

IPs are hard to track. You&#039;ve gotta know what you&#039;re looking for. This guy&#039;s new but he&#039;s not stupid. In all likelihood, he&#039;s using a proxy to get at wp-admin.php. Even if someone found the IP of the proxy he&#039;s using, there are thousands of proxies out there that he can use. Blocking them all is impossible. 

As for investigating it, that&#039;s rather difficult. I know that my webhost control panel isn&#039;t that great at tracking IPs and I bet the ones used on GW and MA aren&#039;t either (mine only records the last 300 visitors). Seeing as how the the vulnerabilities were found in Wordpress and not with the site itself, I doubt any host or ISP would launch such an investigation. There&#039;s no place to start. 

Of course, I&#039;m not an expert or anything, so take all of this with a grain of salt.</description>
		<content:encoded><![CDATA[<p>I hate to break it to you but I think you&#8217;re wrong. None of this is staged. </p>
<p>IPs are hard to track. You&#8217;ve gotta know what you&#8217;re looking for. This guy&#8217;s new but he&#8217;s not stupid. In all likelihood, he&#8217;s using a proxy to get at wp-admin.php. Even if someone found the IP of the proxy he&#8217;s using, there are thousands of proxies out there that he can use. Blocking them all is impossible. </p>
<p>As for investigating it, that&#8217;s rather difficult. I know that my webhost control panel isn&#8217;t that great at tracking IPs and I bet the ones used on GW and MA aren&#8217;t either (mine only records the last 300 visitors). Seeing as how the the vulnerabilities were found in WordPress and not with the site itself, I doubt any host or ISP would launch such an investigation. There&#8217;s no place to start. </p>
<p>Of course, I&#8217;m not an expert or anything, so take all of this with a grain of salt.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
