<?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 2.1.2 Upgrade</title>
	<atom:link href="http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/</link>
	<description></description>
	<lastBuildDate>Sat, 14 May 2011 00:59:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Philip</title>
		<link>http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/comment-page-1/#comment-3671</link>
		<dc:creator>Philip</dc:creator>
		<pubDate>Tue, 27 Mar 2007 17:06:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/#comment-3671</guid>
		<description>Well, I upgraded my site without any issues this weekend.  None of my plugins broke.  I was lucky.</description>
		<content:encoded><![CDATA[<p>Well, I upgraded my site without any issues this weekend.  None of my plugins broke.  I was lucky.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zack Rippy</title>
		<link>http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/comment-page-1/#comment-3618</link>
		<dc:creator>Zack Rippy</dc:creator>
		<pubDate>Tue, 20 Mar 2007 03:39:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/#comment-3618</guid>
		<description>Hey man,

The wp_get_links thing drove me nuts at first. I was pulling my hair out. Fortunately, other (best) Wordpress admins had dealt with it before. :)

The security issue is a very interesting incident. Unless someone had an insanely insecure password, it surely took at least a moderate level of skill to get it and do the damage. Obviously, I know nothing about Wordpress&#039; distribution system, but still...

I don&#039;t want to encourage or condone such things, but for some reason, such stories are always a bit amusing to me...and then I run off and check every server I manage to make sure I haven&#039;t been just completely owned! :)</description>
		<content:encoded><![CDATA[<p>Hey man,</p>
<p>The wp_get_links thing drove me nuts at first. I was pulling my hair out. Fortunately, other (best) WordPress admins had dealt with it before. <img src='http://www.zackrippy.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The security issue is a very interesting incident. Unless someone had an insanely insecure password, it surely took at least a moderate level of skill to get it and do the damage. Obviously, I know nothing about WordPress&#8217; distribution system, but still&#8230;</p>
<p>I don&#8217;t want to encourage or condone such things, but for some reason, such stories are always a bit amusing to me&#8230;and then I run off and check every server I manage to make sure I haven&#8217;t been just completely owned! <img src='http://www.zackrippy.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Russell</title>
		<link>http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/comment-page-1/#comment-3545</link>
		<dc:creator>David Russell</dc:creator>
		<pubDate>Fri, 16 Mar 2007 15:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.zackrippy.com/2007/03/16/wordpress-212-upgrade/#comment-3545</guid>
		<description>Hey thanks for paving the way on this. I think I am using the wp_get_links function in a few places, so I&#039;ll be watching for that and fix accordingly.

As to the security issue, I&#039;ve really thought about blogging about that, even though it&#039;s been in the news a few days now. It&#039;s such a strange event and rare to hear about. I certainly don&#039;t want to give undue credit to the cracker, but breaking into WordPress.org and inserting malicious code into a source package is not manageable by a novice. I am glad to hear of the WordPress team&#039;s response and plan of action. I think that should solve it.</description>
		<content:encoded><![CDATA[<p>Hey thanks for paving the way on this. I think I am using the wp_get_links function in a few places, so I&#8217;ll be watching for that and fix accordingly.</p>
<p>As to the security issue, I&#8217;ve really thought about blogging about that, even though it&#8217;s been in the news a few days now. It&#8217;s such a strange event and rare to hear about. I certainly don&#8217;t want to give undue credit to the cracker, but breaking into WordPress.org and inserting malicious code into a source package is not manageable by a novice. I am glad to hear of the WordPress team&#8217;s response and plan of action. I think that should solve it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

