<?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"
	>
<channel>
	<title>Comments on: Nasty little spammers</title>
	<atom:link href="http://www.splee.co.uk/2008/07/23/nasty-little-spammers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.splee.co.uk/2008/07/23/nasty-little-spammers/</link>
	<description>Bring out the g33k</description>
	<pubDate>Thu, 20 Nov 2008 16:34:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Splee</title>
		<link>http://www.splee.co.uk/2008/07/23/nasty-little-spammers/#comment-34221</link>
		<dc:creator>Splee</dc:creator>
		<pubDate>Mon, 28 Jul 2008 08:04:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.splee.co.uk/?p=271#comment-34221</guid>
		<description>@Daniel I've read a lot of forum posts (admittedly quite old) that point the finger at XML-RPC as the source of at least some of these types of attack.  Some (if not all) of these security holes may have been fixed, but I think this has been going on for a while given the timestamps on the modified files so I really have no way of knowing what caused the issue.

However, in the interest of not spreading FUD, I'm going to update my post as I can't be certain that XML-RPC was to blame.

I'm also going to be enabling XML-RPC again to try out MarsEdit as I really liked the application once I got it working =)</description>
		<content:encoded><![CDATA[<p>@Daniel I&#8217;ve read a lot of forum posts (admittedly quite old) that point the finger at XML-RPC as the source of at least some of these types of attack.  Some (if not all) of these security holes may have been fixed, but I think this has been going on for a while given the timestamps on the modified files so I really have no way of knowing what caused the issue.</p>
<p>However, in the interest of not spreading FUD, I&#8217;m going to update my post as I can&#8217;t be certain that XML-RPC was to blame.</p>
<p>I&#8217;m also going to be enabling XML-RPC again to try out MarsEdit as I really liked the application once I got it working =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Jalkut</title>
		<link>http://www.splee.co.uk/2008/07/23/nasty-little-spammers/#comment-34220</link>
		<dc:creator>Daniel Jalkut</dc:creator>
		<pubDate>Thu, 24 Jul 2008 03:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.splee.co.uk/?p=271#comment-34220</guid>
		<description>Sorry to hear you were hacked ;( I was hacked recently as well.  You might be interested to know though that I talked to some folks on the WordPress team about the security of XMLRPC, and as far as they know none of these hacks is happening *because* of XMLRPC, even though as you witnessed they sometimes screw up the XMLRPC results.

More likely the blog got compromised before you updated to 2.6, and it infected one of your plugins, or installed a bogus plugin that is re-infecting you. It's hard to say, but in any case I wouldn't make the assume you're improving the security by turning off XMLRPC.

Daniel</description>
		<content:encoded><![CDATA[<p>Sorry to hear you were hacked ;( I was hacked recently as well.  You might be interested to know though that I talked to some folks on the WordPress team about the security of XMLRPC, and as far as they know none of these hacks is happening <em>because</em> of XMLRPC, even though as you witnessed they sometimes screw up the XMLRPC results.</p>
<p>More likely the blog got compromised before you updated to 2.6, and it infected one of your plugins, or installed a bogus plugin that is re-infecting you. It&#8217;s hard to say, but in any case I wouldn&#8217;t make the assume you&#8217;re improving the security by turning off XMLRPC.</p>
<p>Daniel</p>
]]></content:encoded>
	</item>
</channel>
</rss>
