<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blogging Extreme.com &#187; Security</title>
	<atom:link href="http://bloggingextreme.com/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://bloggingextreme.com</link>
	<description>Blogging Extreme.com ★ The Location For Learning Extreme Blogging ★</description>
	<lastBuildDate>Tue, 23 Feb 2010 03:54:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WordPress 2.8.4: Security Release</title>
		<link>http://wordpress.org/development/2009/08/2-8-4-security-release/</link>
		<comments>http://wordpress.org/development/2009/08/2-8-4-security-release/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 01:41:54 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[Releases]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://wordpress.org/development/?p=903</guid>
		<description><![CDATA[Yesterday a vulnerability was discovered: a specially crafted URL could be requested that would allow an attacker to bypass a security check to verify a user requested a password reset. As a result, the first account without a key in the database (usually the admin account) would have its password reset and a new password [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday a vulnerability was discovered: a specially crafted URL could be requested that would allow an attacker to bypass a security check to verify a user requested a password reset. As a result, the first account without a key in the database (usually the admin account) would have its password reset and a new password would be emailed to the account owner. This doesn&#8217;t allow remote access, but it is very annoying.</p>
<p>We fixed this problem last night and have been testing the fixes and looking for other problems since then. <a href="http://wordpress.org/download/">Version 2.8.4 which fixes all known problems is now available for download</a> and is highly recommended for all users of WordPress.</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpress.org/development/2009/08/2-8-4-security-release/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The WordPress 2.0.x Legacy Branch is Deprecated</title>
		<link>http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/</link>
		<comments>http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 01:07:23 +0000</pubDate>
		<dc:creator>Mark Jaquith</dc:creator>
				<category><![CDATA[2.0]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[branch]]></category>
		<category><![CDATA[deprecation]]></category>
		<category><![CDATA[legacy]]></category>

		<guid isPermaLink="false">http://wordpress.org/development/?p=866</guid>
		<description><![CDATA[The WordPress team had initially committed to maintaining the WordPress 2.0.x legacy branch until 2010. Unfortunately, we bit off more than we could chew—the 2.0.x branch is now retired and deprecated, a few months shy of 2010.
Many of the security improvements to the new versions of WordPress in the last couple of years were complete [...]]]></description>
			<content:encoded><![CDATA[<p>The WordPress team had initially committed to maintaining the WordPress 2.0.x legacy branch until 2010. Unfortunately, we bit off more than we could chew—the 2.0.x branch is now retired and deprecated, a few months shy of 2010.</p>
<p>Many of the security improvements to the new versions of WordPress in the last couple of years were complete reworks of how various systems were handled. Porting those changes to the 2.0.x branch would have been a monumental task and could have introduced instability or new bugs. We had to make hard decisions between stability and merging in the latest security enhancements. Additionally, far fewer people stayed on the 2.0.x branch than we anticipated. I take that as a testament to the new features in WordPress and perhaps even more the features offered by plugins, many of which don&#8217;t support older versions of WordPress!</p>
<p>I&#8217;m disappointed that we weren&#8217;t able to keep the branch maintained until 2010, but since one of the big reasons for that failure was the massive scope of our security improvements for the newer versions of WordPress, 2.0.x doesn&#8217;t die in vain!</p>
]]></content:encoded>
			<wfw:commentRss>http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
