<?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: Techcrunch Says WordPress a Massive Security Risk</title>
	<atom:link href="http://www.allthingscahill.com/2008/06/techcrunch-says-wordpress-a-massive-security-risk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allthingscahill.com/2008/06/techcrunch-says-wordpress-a-massive-security-risk/</link>
	<description>The online home for Mark Cahill, and indeed, all things Cahill!</description>
	<lastBuildDate>Wed, 08 Feb 2012 18:48:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Cahill</title>
		<link>http://www.allthingscahill.com/2008/06/techcrunch-says-wordpress-a-massive-security-risk/comment-page-1/#comment-505</link>
		<dc:creator>Mark Cahill</dc:creator>
		<pubDate>Wed, 18 Jun 2008 19:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.allthingscahill.com/?p=525#comment-505</guid>
		<description>I&#039;m going to say at this point the article was a scurrilous attack on Automattic - seeing as the author did not respond to direct article comments asking for clarification.

I ran a Developer Brown Bag on Wordpress Security with my team today and we went over many of the most recent security issues.  Very interesting stuff - and most of the attacks would require either someone to release a package script (for the script kiddies) or a very serious knowledge of coding.  

The bottom line: 

1. Stay up to date
2. Use only plugins in general release and keep them up to date.
3. Htaccess protect wp-admin
4. Use as few plugins as possible (Do you hear me, DC!)
5. Back up and always assume you could lose the stuff on the webserver at any point.
6. If you use other software, or code yourself, be sure every single form field is protected properly against SQL Injection Attacks.</description>
		<content:encoded><![CDATA[<p>I&#8217;m going to say at this point the article was a scurrilous attack on Automattic &#8211; seeing as the author did not respond to direct article comments asking for clarification.</p>
<p>I ran a Developer Brown Bag on WordPress Security with my team today and we went over many of the most recent security issues.  Very interesting stuff &#8211; and most of the attacks would require either someone to release a package script (for the script kiddies) or a very serious knowledge of coding.  </p>
<p>The bottom line: </p>
<p>1. Stay up to date<br />
2. Use only plugins in general release and keep them up to date.<br />
3. Htaccess protect wp-admin<br />
4. Use as few plugins as possible (Do you hear me, DC!)<br />
5. Back up and always assume you could lose the stuff on the webserver at any point.<br />
6. If you use other software, or code yourself, be sure every single form field is protected properly against SQL Injection Attacks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Esteban</title>
		<link>http://www.allthingscahill.com/2008/06/techcrunch-says-wordpress-a-massive-security-risk/comment-page-1/#comment-504</link>
		<dc:creator>Esteban</dc:creator>
		<pubDate>Wed, 18 Jun 2008 16:08:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.allthingscahill.com/?p=525#comment-504</guid>
		<description>In my own experience Automattic is extremely quick in fixing security holes. For instance they jumped from 2.5 to 2.5.1 in less than a month due to the security risks they found...</description>
		<content:encoded><![CDATA[<p>In my own experience Automattic is extremely quick in fixing security holes. For instance they jumped from 2.5 to 2.5.1 in less than a month due to the security risks they found&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Austin</title>
		<link>http://www.allthingscahill.com/2008/06/techcrunch-says-wordpress-a-massive-security-risk/comment-page-1/#comment-502</link>
		<dc:creator>Austin</dc:creator>
		<pubDate>Fri, 13 Jun 2008 17:05:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.allthingscahill.com/?p=525#comment-502</guid>
		<description>Not all the issues are over a year old, but &lt;a href=&quot;http://pressedwords.com/techcrunch-on-wordpress-security/&quot; rel=&quot;nofollow&quot;&gt;as I discovered&lt;/a&gt;, all the blogs he cites as attacked had been running outdated versions of WordPress for a while.</description>
		<content:encoded><![CDATA[<p>Not all the issues are over a year old, but <a href="http://pressedwords.com/techcrunch-on-wordpress-security/" rel="nofollow">as I discovered</a>, all the blogs he cites as attacked had been running outdated versions of WordPress for a while.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

