<?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: WordPress Gets Hacked</title>
	<atom:link href="http://military.rightpundits.com/2008/04/15/wordpress-gets-hacked/feed/" rel="self" type="application/rss+xml" />
	<link>http://military.rightpundits.com/2008/04/15/wordpress-gets-hacked/</link>
	<description></description>
	<pubDate>Sun, 05 Jul 2009 05:11:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: rightwingprof</title>
		<link>http://military.rightpundits.com/2008/04/15/wordpress-gets-hacked/comment-page-1/#comment-122395</link>
		<dc:creator>rightwingprof</dc:creator>
		<pubDate>Wed, 16 Apr 2008 18:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://military.rightpundits.com/?p=2763#comment-122395</guid>
		<description>I suspect I got the spam -- very weird URLs with long alphanumeric strings -- but I didn't get hacked.</description>
		<content:encoded><![CDATA[<p>I suspect I got the spam &#8212; very weird URLs with long alphanumeric strings &#8212; but I didn&#8217;t get hacked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William Teach</title>
		<link>http://military.rightpundits.com/2008/04/15/wordpress-gets-hacked/comment-page-1/#comment-122109</link>
		<dc:creator>William Teach</dc:creator>
		<pubDate>Tue, 15 Apr 2008 23:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://military.rightpundits.com/?p=2763#comment-122109</guid>
		<description>Is that what happened to you, Beth C, and McCain Blogs? Figured it was just a server error, like had been happening with Dreamhost.

I had someone sneak some crap in somewhere, messed up my .htaccess file, and hid stuff somewhere, could never find it, but showed all sorts of evil links within the source code.

Best thing to do is make sure you keep a copy of your htaccess file, have a long, hard password for your blog, ftp access, and host access. Also, make backups of your blog themes, of course.

Your source code looks OK. I'd highly recommend Bad Behavior 2.0.14 and Peter's Anti Spam comments (http://www.theblog.ca/?p=21) plugin. Also, one that closes comments after so many days, such as Comments Timeout (http://beingmrkenny.co.uk/wordpress/plugins/extended-comment-options/)

Those 3 would cut your spam down a lot.

As always, if thou needeth helpeth, let me know, lass!</description>
		<content:encoded><![CDATA[<p>Is that what happened to you, Beth C, and McCain Blogs? Figured it was just a server error, like had been happening with Dreamhost.</p>
<p>I had someone sneak some crap in somewhere, messed up my .htaccess file, and hid stuff somewhere, could never find it, but showed all sorts of evil links within the source code.</p>
<p>Best thing to do is make sure you keep a copy of your htaccess file, have a long, hard password for your blog, ftp access, and host access. Also, make backups of your blog themes, of course.</p>
<p>Your source code looks OK. I&#8217;d highly recommend Bad Behavior 2.0.14 and Peter&#8217;s Anti Spam comments (http://www.theblog.ca/?p=21) plugin. Also, one that closes comments after so many days, such as Comments Timeout (http://beingmrkenny.co.uk/wordpress/plugins/extended-comment-options/)</p>
<p>Those 3 would cut your spam down a lot.</p>
<p>As always, if thou needeth helpeth, let me know, lass!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leanne</title>
		<link>http://military.rightpundits.com/2008/04/15/wordpress-gets-hacked/comment-page-1/#comment-121919</link>
		<dc:creator>Leanne</dc:creator>
		<pubDate>Tue, 15 Apr 2008 12:10:31 +0000</pubDate>
		<guid isPermaLink="false">http://military.rightpundits.com/?p=2763#comment-121919</guid>
		<description>Dang - I'm sorry that it happened to you, too!  

I am also being told that when upgrading - it is HIGHLY advised to completely delete everything but the wp-config file and upload the fresh upgrade to ensure any files that were hacked are gone and avoid future vulnerabilities.

I have detailed/simple instructions on upgrading as well - if you need the link to them let me know.</description>
		<content:encoded><![CDATA[<p>Dang - I&#8217;m sorry that it happened to you, too!  </p>
<p>I am also being told that when upgrading - it is HIGHLY advised to completely delete everything but the wp-config file and upload the fresh upgrade to ensure any files that were hacked are gone and avoid future vulnerabilities.</p>
<p>I have detailed/simple instructions on upgrading as well - if you need the link to them let me know.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
