<?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: Wordpress 2.04 Beta 2 includes a vital security fix.</title>
	<atom:link href="http://www.thecodecave.com/article220/feed" rel="self" type="application/rss+xml" />
	<link>http://www.thecodecave.com/article220</link>
	<description>Cold storage before my best ideas melt away...</description>
	<pubDate>Mon, 01 Dec 2008 23:44:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: guvenlik sistemleri</title>
		<link>http://www.thecodecave.com/article220#comment-64747</link>
		<dc:creator>guvenlik sistemleri</dc:creator>
		<pubDate>Fri, 08 Aug 2008 22:08:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thecodecave.com/article220#comment-64747</guid>
		<description>Thank you for your post it is valuable information for me</description>
		<content:encoded><![CDATA[<p>Thank you for your post it is valuable information for me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Digital Ramble &#187; Blog Archive &#187; wordpress security issue revisited</title>
		<link>http://www.thecodecave.com/article220#comment-648</link>
		<dc:creator>Digital Ramble &#187; Blog Archive &#187; wordpress security issue revisited</dc:creator>
		<pubDate>Fri, 28 Jul 2006 17:42:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.thecodecave.com/article220#comment-648</guid>
		<description>[...] OK, thanks to Brian Layman who did some additional detective work, it turns out there&#8217;s a beta release available to plug the security issue. I haven&#8217;t installed it yet since I&#8217;m not in the position of being seriously compromised by having lots of registered users or comment activity, but for those WordPress bloggers with bigger setups or who don&#8217;t want to use the workaround, there are beta versions of WP 2.0.4 (which itself looks to have a stable release out in a few days, which is what I&#8217;m waiting for). Check Brian&#8217;s article for the latest beta downloads, it looks like they&#8217;re being pretty frequently updated right now. [...]</description>
		<content:encoded><![CDATA[<p>[...] OK, thanks to Brian Layman who did some additional detective work, it turns out there&#8217;s a beta release available to plug the security issue. I haven&#8217;t installed it yet since I&#8217;m not in the position of being seriously compromised by having lots of registered users or comment activity, but for those WordPress bloggers with bigger setups or who don&#8217;t want to use the workaround, there are beta versions of WP 2.0.4 (which itself looks to have a stable release out in a few days, which is what I&#8217;m waiting for). Check Brian&#8217;s article for the latest beta downloads, it looks like they&#8217;re being pretty frequently updated right now. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://www.thecodecave.com/article220#comment-646</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Fri, 28 Jul 2006 16:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thecodecave.com/article220#comment-646</guid>
		<description>Beta 3 was released 7 minutes ago at 12:38pm EST/16:38 UTC.  I've updated the links above to point at beta3.  The only change between b2 and b3 is a minor fix I tested and improved for Ryan last night.  In some rare circumstances the author link at the bottom of the posts might have been incorrect.  Those of us without themes that support multiple authors would be unaffected by this change.  So, there's no real reason to get b3 if you have b2 installed already.  The release MAY come sooner than I mentioned in this article.  Perhaps by as much as 3 days sooner...but I wouldn't mind another evening just to try to exploit this version.</description>
		<content:encoded><![CDATA[<p>Beta 3 was released 7 minutes ago at 12:38pm EST/16:38 UTC.  I&#8217;ve updated the links above to point at beta3.  The only change between b2 and b3 is a minor fix I tested and improved for Ryan last night.  In some rare circumstances the author link at the bottom of the posts might have been incorrect.  Those of us without themes that support multiple authors would be unaffected by this change.  So, there&#8217;s no real reason to get b3 if you have b2 installed already.  The release MAY come sooner than I mentioned in this article.  Perhaps by as much as 3 days sooner&#8230;but I wouldn&#8217;t mind another evening just to try to exploit this version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gattaca</title>
		<link>http://www.thecodecave.com/article220#comment-637</link>
		<dc:creator>gattaca</dc:creator>
		<pubDate>Fri, 28 Jul 2006 10:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.thecodecave.com/article220#comment-637</guid>
		<description>Thanks for the clarification. I'm fairly used to people overreacting on the security front. It's always good to get a level setting before the FUD takes over. That being said I have to head back into my bunker before they detect my presence on the surface. :D 

Thanks for the trackback.

cheers</description>
		<content:encoded><![CDATA[<p>Thanks for the clarification. I&#8217;m fairly used to people overreacting on the security front. It&#8217;s always good to get a level setting before the FUD takes over. That being said I have to head back into my bunker before they detect my presence on the surface. <img src='http://www.thecodecave.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>Thanks for the trackback.</p>
<p>cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liquidmatrix Security Digest</title>
		<link>http://www.thecodecave.com/article220#comment-636</link>
		<dc:creator>Liquidmatrix Security Digest</dc:creator>
		<pubDate>Fri, 28 Jul 2006 10:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.thecodecave.com/article220#comment-636</guid>
		<description>[...] UPDATE: OK, now I have a much better idea. Thanks to this posting by Bryan Layman at the Code Cave we have some actual information rather than the Chicken Little approach.  The really good news is that Ryan Boren released the beta version of WordPress 2.0.4 on Sunday. The Beta2 version of the release includes a fix for this issue. [...]</description>
		<content:encoded><![CDATA[<p>[...] UPDATE: OK, now I have a much better idea. Thanks to this posting by Bryan Layman at the Code Cave we have some actual information rather than the Chicken Little approach.  The really good news is that Ryan Boren released the beta version of WordPress 2.0.4 on Sunday. The Beta2 version of the release includes a fix for this issue. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Collin</title>
		<link>http://www.thecodecave.com/article220#comment-631</link>
		<dc:creator>Collin</dc:creator>
		<pubDate>Fri, 28 Jul 2006 06:58:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thecodecave.com/article220#comment-631</guid>
		<description>Thanks for the trackback. :)

For my part, I don't have any other registered users.  It's only me that writes my blog and I have never seen the point of becoming a subscriber on someone else's blog.

When someone like Dr Dave releases the information then I'm gonna take it kind of seriously.  It was simple enough just to nip into my dashboard and turn the option off.

If/when the bug gets fixed I can turn it back on.  By spreading the word we can hopefully stop the bug becoming a big problem.

I am running 2.0.3 but I'm not going to update to 2.0.4 yet, I am one of those people that likes stable releases.  I've played with the beta on my local testing server, but will wait to do my live blogs.

That said, I'm not sure my photoblog is up-to-date.... Oops!</description>
		<content:encoded><![CDATA[<p>Thanks for the trackback. <img src='http://www.thecodecave.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>For my part, I don&#8217;t have any other registered users.  It&#8217;s only me that writes my blog and I have never seen the point of becoming a subscriber on someone else&#8217;s blog.</p>
<p>When someone like Dr Dave releases the information then I&#8217;m gonna take it kind of seriously.  It was simple enough just to nip into my dashboard and turn the option off.</p>
<p>If/when the bug gets fixed I can turn it back on.  By spreading the word we can hopefully stop the bug becoming a big problem.</p>
<p>I am running 2.0.3 but I&#8217;m not going to update to 2.0.4 yet, I am one of those people that likes stable releases.  I&#8217;ve played with the beta on my local testing server, but will wait to do my live blogs.</p>
<p>That said, I&#8217;m not sure my photoblog is up-to-date&#8230;. Oops!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.305 seconds -->
