<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: WordPress to Disable XMLRPC by Default?</title>
	<atom:link href="http://www.cogniview.com/convert-pdf-to-excel/post/wordpress-to-disable-xmlrpc-by-default/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cogniview.com/convert-pdf-to-excel/post/wordpress-to-disable-xmlrpc-by-default/</link>
	<description>Excel(lent) Stuff</description>
	<lastBuildDate>Thu, 29 Jul 2010 14:42:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cimmeron</title>
		<link>http://www.cogniview.com/convert-pdf-to-excel/post/wordpress-to-disable-xmlrpc-by-default/comment-page-1/#comment-93452</link>
		<dc:creator>Cimmeron</dc:creator>
		<pubDate>Tue, 29 Jul 2008 22:56:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.cogniview.com/convert-pdf-to-excel/?p=219#comment-93452</guid>
		<description>Wordpress 2.6 is supposed to (rumor has it) fix the potential of a SQL injection attack.  I wonder if this has to do with the XMLRPC?  I cannot seem to find any information anywhere on Wordpress.org that specifically addresses the huge issue this caused recently.  Maybe they don&#039;t want to admit to such a huge hole?  or am I just missing something? :)</description>
		<content:encoded><![CDATA[<p>Wordpress 2.6 is supposed to (rumor has it) fix the potential of a SQL injection attack.  I wonder if this has to do with the XMLRPC?  I cannot seem to find any information anywhere on Wordpress.org that specifically addresses the huge issue this caused recently.  Maybe they don&#8217;t want to admit to such a huge hole?  or am I just missing something? <img src='http://www.cogniview.com/convert-pdf-to-excel/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik</title>
		<link>http://www.cogniview.com/convert-pdf-to-excel/post/wordpress-to-disable-xmlrpc-by-default/comment-page-1/#comment-84270</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Thu, 03 Jul 2008 08:44:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.cogniview.com/convert-pdf-to-excel/?p=219#comment-84270</guid>
		<description>While I&#039;m not clued up about the finer details of XMLRPC, almost every feature you have in software is a potential security threat. A feature that allows remote administration incredibly so. 

Simply put, the fewer features like that, the less hackable you are, as the (jargon alert) &quot;attack vector&quot; is reduced. 

Some horrible attacks (Code Red for example) have occurred due to seemingly innocuous features.

It&#039;s just good practice to start with only what you need, and open features as required. 

I can understand Ecto&#039;s point of view, but on the whole, if people loose faith in Wordpress, that doesn&#039;t help them either.

If I recall correctly, there have been at least one serious wordpress vulnerability recently, so they&#039;re probably trying to make sure it doesn&#039;t happen again.</description>
		<content:encoded><![CDATA[<p>While I&#8217;m not clued up about the finer details of XMLRPC, almost every feature you have in software is a potential security threat. A feature that allows remote administration incredibly so. </p>
<p>Simply put, the fewer features like that, the less hackable you are, as the (jargon alert) &#8220;attack vector&#8221; is reduced. </p>
<p>Some horrible attacks (Code Red for example) have occurred due to seemingly innocuous features.</p>
<p>It&#8217;s just good practice to start with only what you need, and open features as required. </p>
<p>I can understand Ecto&#8217;s point of view, but on the whole, if people loose faith in Wordpress, that doesn&#8217;t help them either.</p>
<p>If I recall correctly, there have been at least one serious wordpress vulnerability recently, so they&#8217;re probably trying to make sure it doesn&#8217;t happen again.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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