<?xml version="1.0"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>Wriging Thread: Movable Type Security Trumps WordPress, Not Much Of A Newsflash</title>
<link>http://wriging.com/notes/</link>
<description>Wriging Thread: Movable Type Security Trumps WordPress, Not Much Of A Newsflash</description>
<language>en</language>
<pubDate>Thu, 08 Jan 2009 08:19:38 +0000</pubDate>

<item>
<title>Movable Type Security Trumps WordPress, Not Much Of A Newsflash</title>
<link>http://wriging.com/blogging/notes/15007/p/1/#response-117726</link>
<pubDate>Sat, 14 Jun 2008 00:55:05</pubDate>
<dc:creator>davidhayes</dc:creator>
<guid isPermaLink="false">117726</guid>
<description>&lt;p&gt;I was going to throw in the zinger: &quot;It's easy to be secure when you've not added features in years.&quot;&lt;/p&gt;
&lt;p&gt;But Scrivs makes a good point. WordPress, like Windows, suffers from the fact that everyone uses it, and not everyone keeps it up-to-date. The developers actually do an admirable job patching stuff, but that's doesn't stop blogs running WordPress 2.2.1 from suffering from already-patched vulnerabilities.
&lt;/p&gt;</description>
</item>
<item>
<title>Movable Type Security Trumps WordPress, Not Much Of A Newsflash</title>
<link>http://wriging.com/blogging/notes/15007/p/1/#response-117674</link>
<pubDate>Fri, 13 Jun 2008 05:53:55</pubDate>
<dc:creator>Scrivs</dc:creator>
<guid isPermaLink="false">117674</guid>
<description>&lt;p&gt;Well WP has the unfortunate distinction of being the Windows of the blogging scene and by this I mean most widely used platform and therefore one that is going to be most susceptible to attacks. When the code is Open Source it makes it easier to find holes, but also makes it easier to patch them up.
&lt;/p&gt;</description>
</item>
<item>
<title>Movable Type Security Trumps WordPress, Not Much Of A Newsflash</title>
<link>http://wriging.com/blogging/notes/15007/p/1/#response-117666</link>
<pubDate>Fri, 13 Jun 2008 05:46:56</pubDate>
<dc:creator>Mike</dc:creator>
<guid isPermaLink="false">117666</guid>
<description>&lt;p&gt;I just left a comment over at Anil Dash's entry at the Movable Type blog about this and I think it's worth reiterating here at Wriging for others to see.&lt;/p&gt;
&lt;p&gt;The problems that WordPress is currently having with security really need to be scrutinized because &lt;a href=&quot;http://article.gmane.org/gmane.linux.debian.devel.bugs.general/428015&quot;&gt;huge security issues like this one&lt;/a&gt; are a bad thing.  WP has released an update to address that issue but the bottom line is that if you allowed users to register on your site they could potentially modify their cookie and trick your WP blog into thinking they were authenticated into &lt;em&gt;a different account&lt;/em&gt; and then gain administrative rights over your site.  Ouch.  Let's hope you downloaded that update.
&lt;/p&gt;</description>
</item>

</channel>
</rss>

