<?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: Don&#8217;t Panic! WordPress Is Secure</title>
	<atom:link href="http://wordpress.org/development/2005/11/wordpress-is-secure/feed/" rel="self" type="application/rss+xml" />
	<link>http://wordpress.org/development/2005/11/wordpress-is-secure/</link>
	<description>WordPress development and updates</description>
	<lastBuildDate>Sat, 07 Nov 2009 00:50:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9-rare</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: XML-RPC Worm - Simone Carletti&#8217;s Blog</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-6/#comment-41825</link>
		<dc:creator>XML-RPC Worm - Simone Carletti&#8217;s Blog</dc:creator>
		<pubDate>Sun, 11 Jan 2009 14:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-41825</guid>
		<description>[...] utilizzate WordPress il team di sviluppo assicura che il virus non affligge i possessori di tale piattaforma. E le altre? Al momento non ci sono [...]</description>
		<content:encoded><![CDATA[<p>[...] utilizzate WordPress il team di sviluppo assicura che il virus non affligge i possessori di tale piattaforma. E le altre? Al momento non ci sono [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linux worm targets PHP based application</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-6/#comment-25049</link>
		<dc:creator>Linux worm targets PHP based application</dc:creator>
		<pubDate>Sun, 02 Dec 2007 19:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-25049</guid>
		<description>[...] blog software is secure from this attack  Read the McAfee report here. More coverage is here and [...]</description>
		<content:encoded><![CDATA[<p>[...] blog software is secure from this attack  Read the McAfee report here. More coverage is here and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alvanweb &#187; ÛŒØ§Ù‡Ùˆ Ùˆ ÙˆØ±Ø¯Ù¾Ø±Ø³</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-6/#comment-3052</link>
		<dc:creator>Alvanweb &#187; ÛŒØ§Ù‡Ùˆ Ùˆ ÙˆØ±Ø¯Ù¾Ø±Ø³</dc:creator>
		<pubDate>Sun, 04 Dec 2005 15:49:54 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3052</guid>
		<description>[...] Ø¨Ø§ Ø§ÛŒÙ† Ú©Ø§Ø±Ø´ Ù†Ø´ÙˆÙ† Ø¯Ø§Ø¯ ÙˆØ±Ø¯Ù¾Ø±Ø³ Ø­Ø¯Ø§Ù‚Ù„ Ø§Ø² Ù„Ø­Ø§Ø¸ Ø§Ù…Ù†ÛŒØª Ú†ÛŒÙ‡!   Ù„ÛŒÙ†Ú© ÛŒØ§Ø¯Ø¯Ø§Ø´Øª &#124; Ø¯Ø³ØªÙ‡: ÙˆØ±Ø¯Ù¾Ø±Ø³ &#124; Ù†ÙˆÛŒØ³Ù†Ø¯Ù‡: Ù…Ø±ØªØ¶ÛŒØ§Ù„ÙˆØ§Ù†ÛŒ [...]</description>
		<content:encoded><![CDATA[<p>[...] Ø¨Ø§ Ø§ÛŒÙ† Ú©Ø§Ø±Ø´ Ù†Ø´ÙˆÙ† Ø¯Ø§Ø¯ ÙˆØ±Ø¯Ù¾Ø±Ø³ Ø­Ø¯Ø§Ù‚Ù„ Ø§Ø² Ù„Ø­Ø§Ø¸ Ø§Ù…Ù†ÛŒØª Ú†ÛŒÙ‡!   Ù„ÛŒÙ†Ú© ÛŒØ§Ø¯Ø¯Ø§Ø´Øª | Ø¯Ø³ØªÙ‡: ÙˆØ±Ø¯Ù¾Ø±Ø³ | Ù†ÙˆÛŒØ³Ù†Ø¯Ù‡: Ù…Ø±ØªØ¶ÛŒØ§Ù„ÙˆØ§Ù†ÛŒ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Order of the Bath &#187; Blog Archive &#187; WordPress is secure?</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-6/#comment-3048</link>
		<dc:creator>Order of the Bath &#187; Blog Archive &#187; WordPress is secure?</dc:creator>
		<pubDate>Fri, 02 Dec 2005 09:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3048</guid>
		<description>[...] My Dashboard tells me Don?t Panic! WordPress Is Secure (24 Days ago). This is talking about BugTraq 14088 29-Jun-2005 which only affected version 1.5.1 and earlier. There have of course been others and will be in the future (no software is immune) but there was a new one a few days ago that is a false alarm. The problem arises because of the confusion of names (a familiar story). The alert is BugTraq 15582 which refers to phpWordPress. This is a commercial publishing management system and they clearly state at the bottom of their home page that they are not affiliated with the open-source program WordPress in any way. Perhaps wordpress.org needs a similar disclaimer. [...]</description>
		<content:encoded><![CDATA[<p>[...] My Dashboard tells me Don?t Panic! WordPress Is Secure (24 Days ago). This is talking about BugTraq 14088 29-Jun-2005 which only affected version 1.5.1 and earlier. There have of course been others and will be in the future (no software is immune) but there was a new one a few days ago that is a false alarm. The problem arises because of the confusion of names (a familiar story). The alert is BugTraq 15582 which refers to phpWordPress. This is a commercial publishing management system and they clearly state at the bottom of their home page that they are not affiliated with the open-source program WordPress in any way. Perhaps wordpress.org needs a similar disclaimer. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Develop-Mental</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-6/#comment-3045</link>
		<dc:creator>Develop-Mental</dc:creator>
		<pubDate>Mon, 28 Nov 2005 09:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3045</guid>
		<description>[...] Recently an exploit was announced affecting PHP&#8217;s xmlrpc interface. WordPress (the makers of this site&#8217;s CMS system) announced their users were not affected [...]</description>
		<content:encoded><![CDATA[<p>[...] Recently an exploit was announced affecting PHP&#8217;s xmlrpc interface. WordPress (the makers of this site&#8217;s CMS system) announced their users were not affected [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimthompson.org</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-6/#comment-3043</link>
		<dc:creator>jimthompson.org</dc:creator>
		<pubDate>Sun, 27 Nov 2005 23:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3043</guid>
		<description>&lt;strong&gt;Blog Strangeness...&lt;/strong&gt;

	I went to jimthompson.org this afternoon to follow a link I had stored there, and instead of the usual WordPress page, I got the following error:
	Warning: main(./wp-blog-header.php): failed to open stream:
Permission denied in /&#8230;/wp/index.php o...</description>
		<content:encoded><![CDATA[<p><strong>Blog Strangeness&#8230;</strong></p>
<p>	I went to jimthompson.org this afternoon to follow a link I had stored there, and instead of the usual WordPress page, I got the following error:<br />
	Warning: main(./wp-blog-header.php): failed to open stream:<br />
Permission denied in /&#8230;/wp/index.php o&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#60;strike&#62;Scott&#8217;s&#60;/strike&#62; JO&#8217;S!!! Blog &#187; Blog Archive &#187; Slow news day.</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-6/#comment-3031</link>
		<dc:creator>&#60;strike&#62;Scott&#8217;s&#60;/strike&#62; JO&#8217;S!!! Blog &#187; Blog Archive &#187; Slow news day.</dc:creator>
		<pubDate>Fri, 18 Nov 2005 11:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3031</guid>
		<description>[...] This was prompted not only because of the pretty new interface (isn&#8217;t it nice!) but most importantly by a security vulnerability. [...]</description>
		<content:encoded><![CDATA[<p>[...] This was prompted not only because of the pretty new interface (isn&#8217;t it nice!) but most importantly by a security vulnerability. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodney Fletcher&#8217;s Blog &#187; Hacked</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-5/#comment-3024</link>
		<dc:creator>Rodney Fletcher&#8217;s Blog &#187; Hacked</dc:creator>
		<pubDate>Tue, 15 Nov 2005 12:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3024</guid>
		<description>[...] This blog is ok (for now&#8230; maybe  )/    &#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] This blog is ok (for now&#8230; maybe  )/    &nbsp; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JonCellini.com &#187; Blog Archive &#187; wp-keitai-mail and the PHPXMLRPC vulnerability</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-5/#comment-3018</link>
		<dc:creator>JonCellini.com &#187; Blog Archive &#187; wp-keitai-mail and the PHPXMLRPC vulnerability</dc:creator>
		<pubDate>Sat, 12 Nov 2005 00:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3018</guid>
		<description>[...] I use Dr. Dave&#8217;s wp-keitai-mail script for my moblog postings which works great; however, it depends on some older XMLRPC files from Wordpress 1.2 which unfortunately are vulnerable to remote code execution that has recently been exploited by a worm making its way around the Internet. It looks like Dr. Dave has lost interest in updating it and trying to rewrite it to use the new WP 1.5 XMLRPC libraries is non-trivial. [...]</description>
		<content:encoded><![CDATA[<p>[...] I use Dr. Dave&#8217;s wp-keitai-mail script for my moblog postings which works great; however, it depends on some older XMLRPC files from Wordpress 1.2 which unfortunately are vulnerable to remote code execution that has recently been exploited by a worm making its way around the Internet. It looks like Dr. Dave has lost interest in updating it and trying to rewrite it to use the new WP 1.5 XMLRPC libraries is non-trivial. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan's Blog</title>
		<link>http://wordpress.org/development/2005/11/wordpress-is-secure/comment-page-5/#comment-3017</link>
		<dc:creator>Jonathan's Blog</dc:creator>
		<pubDate>Fri, 11 Nov 2005 21:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress.org/development/2005/11/wordpress-is-secure/#comment-3017</guid>
		<description>&lt;strong&gt;Wordpress is secure from recent &#8220;blog worm&#8221; attacks&lt;/strong&gt;

	&#8220;Dougal&#8221;, a Wordpress developper, in a post named &#8220;Donâ€™t Panic! WordPress Is Secure&#8221;  reports that Wordpress 1.5 is safe from the recent blog worms.
	I have seen this worm trying to attack me in my Apache logs, if you have a ...</description>
		<content:encoded><![CDATA[<p><strong>Wordpress is secure from recent &#8220;blog worm&#8221; attacks</strong></p>
<p>	&#8220;Dougal&#8221;, a Wordpress developper, in a post named &#8220;Donâ€™t Panic! WordPress Is Secure&#8221;  reports that Wordpress 1.5 is safe from the recent blog worms.<br />
	I have seen this worm trying to attack me in my Apache logs, if you have a &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
