<?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 1.5.1.3 Released</title>
	<atom:link href="http://scott.yang.id.au/2005/06/wordpress-1513-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://scott.yang.id.au/2005/06/wordpress-1513-released/</link>
	<description>Faith, Technology and Randomness in Life, According to Scott</description>
	<lastBuildDate>Tue, 09 Mar 2010 18:56:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: scotty</title>
		<link>http://scott.yang.id.au/2005/06/wordpress-1513-released/comment-page-1/#comment-21669</link>
		<dc:creator>scotty</dc:creator>
		<pubDate>Sat, 27 Aug 2005 08:53:42 +0000</pubDate>
		<guid isPermaLink="false">http://scott.yang.id.au/?p=1095#comment-21669</guid>
		<description>Ivan,

Yes it has certainly fixed the XML-RPC escaping issue. Since 1.5.2 is also a security fix, it is highly recommended to upgrade.</description>
		<content:encoded><![CDATA[<p>Ivan,</p>
<p>Yes it has certainly fixed the XML-RPC escaping issue. Since 1.5.2 is also a security fix, it is highly recommended to upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Pan</title>
		<link>http://scott.yang.id.au/2005/06/wordpress-1513-released/comment-page-1/#comment-21668</link>
		<dc:creator>Ivan Pan</dc:creator>
		<pubDate>Sat, 27 Aug 2005 06:46:12 +0000</pubDate>
		<guid isPermaLink="false">http://scott.yang.id.au/?p=1095#comment-21668</guid>
		<description>WordPress v1.5.2 was released on Aug. 14, 2005. I have no way of testing this since I use a free blogsome blog (for now). Since you are the only one that has same problems as me, can you tell me that if this problem still exist in v1.5.2?</description>
		<content:encoded><![CDATA[<p>WordPress v1.5.2 was released on Aug. 14, 2005. I have no way of testing this since I use a free blogsome blog (for now). Since you are the only one that has same problems as me, can you tell me that if this problem still exist in v1.5.2?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scotty</title>
		<link>http://scott.yang.id.au/2005/06/wordpress-1513-released/comment-page-1/#comment-21471</link>
		<dc:creator>scotty</dc:creator>
		<pubDate>Thu, 30 Jun 2005 01:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://scott.yang.id.au/?p=1095#comment-21471</guid>
		<description>It is indeed quite disappointing - see my update on how Drupal released their security updates, and their detailed reports on each of the patches.

More disappointing is the fix actually breaks more code. Bloody backslashes...</description>
		<content:encoded><![CDATA[<p>It is indeed quite disappointing &#8211; see my update on how Drupal released their security updates, and their detailed reports on each of the patches.</p>
<p>More disappointing is the fix actually breaks more code. Bloody backslashes&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Russell</title>
		<link>http://scott.yang.id.au/2005/06/wordpress-1513-released/comment-page-1/#comment-21470</link>
		<dc:creator>David Russell</dc:creator>
		<pubDate>Wed, 29 Jun 2005 19:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://scott.yang.id.au/?p=1095#comment-21470</guid>
		<description>Yet again, I cannot believe the kind of stuff the WP devs come out with. We&#039;re not telling you what the security vulnerability is, but it is caused by a 4kb PHP file, so if you&#039;re a WP user you won&#039;t find out why you should go through another upgrade, but if you&#039;re a hacker you know where to look to find out how to exploit the vulnerability. Bloody stupid!</description>
		<content:encoded><![CDATA[<p>Yet again, I cannot believe the kind of stuff the WP devs come out with. We&#8217;re not telling you what the security vulnerability is, but it is caused by a 4kb PHP file, so if you&#8217;re a WP user you won&#8217;t find out why you should go through another upgrade, but if you&#8217;re a hacker you know where to look to find out how to exploit the vulnerability. Bloody stupid!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Webmaster-Verzeichnis Blog</title>
		<link>http://scott.yang.id.au/2005/06/wordpress-1513-released/comment-page-1/#comment-21469</link>
		<dc:creator>Webmaster-Verzeichnis Blog</dc:creator>
		<pubDate>Wed, 29 Jun 2005 15:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://scott.yang.id.au/?p=1095#comment-21469</guid>
		<description>&lt;strong&gt;WordPress 1.5.1.3  Security Update&lt;/strong&gt;

WordPress 1.5.1.3 wurde heute veröffentlicht. Diese Version ist ein Sicherheitsupdate und wird von dem Wordpress Team empfohlen. Also gleich mal updaten&#8230;

&gt;&gt; Offizielles Statement und weitere Informationen
&gt;&gt; Deutsche Wordpress
...</description>
		<content:encoded><![CDATA[<p><strong>WordPress 1.5.1.3  Security Update</strong></p>
<p>WordPress 1.5.1.3 wurde heute veröffentlicht. Diese Version ist ein Sicherheitsupdate und wird von dem Wordpress Team empfohlen. Also gleich mal updaten&#8230;</p>
<p>&gt;&gt; Offizielles Statement und weitere Informationen<br />
&gt;&gt; Deutsche Wordpress</p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
