<?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: The xmlrpc.php File and Site Security</title>
	<atom:link href="http://digwp.com/2009/06/xmlrpc-php-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://digwp.com/2009/06/xmlrpc-php-security/</link>
	<description>Take your WordPress skills to the next level.</description>
	<lastBuildDate>Sat, 11 Feb 2012 00:52:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Precision Targeting with Custom Action Hooks &#124; Digging into WordPress</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-1727</link>
		<dc:creator>Precision Targeting with Custom Action Hooks &#124; Digging into WordPress</dc:creator>
		<pubDate>Mon, 21 Sep 2009 05:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-1727</guid>
		<description>[...] WordPress&#8217; powerful action-hook system makes it possible to insert functionality at any point in your theme. Most WordPress themes include some of the built-in WordPress hooks by default. For example, most of us are aware of the two most common WordPress hooks: wp_head() and wp_footer(), which generally appear in the theme&#8217;s header and footer sections. These two hooks provide WordPress a location at which to execute various scripts and functions. For example, the wp_head() hook is where WordPress generates a variety of &lt;link&gt; and &lt;script&gt; elements, among other things. [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress&rsquo; powerful action-hook system makes it possible to insert functionality at any point in your theme. Most WordPress themes include some of the built-in WordPress hooks by default. For example, most of us are aware of the two most common WordPress hooks: wp_head() and wp_footer(), which generally appear in the theme&rsquo;s header and footer sections. These two hooks provide WordPress a location at which to execute various scripts and functions. For example, the wp_head() hook is where WordPress generates a variety of &lt;link&gt; and &lt;script&gt; elements, among other things. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Neng</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-623</link>
		<dc:creator>Luis Neng</dc:creator>
		<pubDate>Fri, 10 Jul 2009 00:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-623</guid>
		<description>Great post! I&#039;m going to apply these modifications in all of my blogs / websites based on Wordpress.

By leaving the xmlrpc.php file on the server but prevent access to it we could always chmod 000 :)</description>
		<content:encoded><![CDATA[<p>Great post! I&#8217;m going to apply these modifications in all of my blogs / websites based on WordPress.</p>
<p>By leaving the xmlrpc.php file on the server but prevent access to it we could always chmod 000 :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-552</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 07 Jul 2009 20:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-552</guid>
		<description>Yep.  I noticed that whether or not I called that function it was breaking other stuff in the admin section as well.  I may have just done something wrong.  Once I removed it everything started working again.  I&#039;ll try it again on my public server when I get the rest of the site built out.</description>
		<content:encoded><![CDATA[<p>Yep.  I noticed that whether or not I called that function it was breaking other stuff in the admin section as well.  I may have just done something wrong.  Once I removed it everything started working again.  I&#8217;ll try it again on my public server when I get the rest of the site built out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Starr</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-550</link>
		<dc:creator>Jeff Starr</dc:creator>
		<pubDate>Tue, 07 Jul 2009 18:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-550</guid>
		<description>Are you referring to the &lt;code&gt;removeHeadLinks()&lt;/code&gt; function? If so, not sure what the issue could be, perhaps you may want to test it on a non-local server?</description>
		<content:encoded><![CDATA[<p>Are you referring to the <code>removeHeadLinks()</code> function? If so, not sure what the issue could be, perhaps you may want to test it on a non-local server?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-548</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 07 Jul 2009 17:28:50 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-548</guid>
		<description>Perhaps I&#039;m misunderstanding but I added the suggested code to my functions.php and renamed xmlrpc.php.  After doing that I get a blank white page.  I&#039;m assuming there is a PHP error somewhere.  This was done on a fresh WP 2.8 install using MAMP</description>
		<content:encoded><![CDATA[<p>Perhaps I&#8217;m misunderstanding but I added the suggested code to my functions.php and renamed xmlrpc.php.  After doing that I get a blank white page.  I&#8217;m assuming there is a PHP error somewhere.  This was done on a fresh WP 2.8 install using MAMP</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The xmlrpc.php File and Site Security</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-486</link>
		<dc:creator>The xmlrpc.php File and Site Security</dc:creator>
		<pubDate>Fri, 03 Jul 2009 17:26:36 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-486</guid>
		<description>[...] the original post: The xmlrpc.php File and Site Security       Tags: seguridad - tips - web     Comments0  Leave a Reply  Click here to cancel [...]</description>
		<content:encoded><![CDATA[<p>[...] the original post: The xmlrpc.php File and Site Security       Tags: seguridad &#8211; tips &#8211; web     Comments0  Leave a Reply  Click here to cancel [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spam Link Injection Hacked (and How I Hopefully Fixed It)</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-365</link>
		<dc:creator>Spam Link Injection Hacked (and How I Hopefully Fixed It)</dc:creator>
		<pubDate>Tue, 30 Jun 2009 13:16:51 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-365</guid>
		<description>[...] XMLRPC file was removed. This file is used for pingback and trackbacks as well as remote editing possibilities like posting by email. I literally [...]</description>
		<content:encoded><![CDATA[<p>[...] XMLRPC file was removed. This file is used for pingback and trackbacks as well as remote editing possibilities like posting by email. I literally [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets from purplehayz on 2009-06-25 &#171; Aleph Naught &#38; the Null Set</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-301</link>
		<dc:creator>Tweets from purplehayz on 2009-06-25 &#171; Aleph Naught &#38; the Null Set</dc:creator>
		<pubDate>Sun, 28 Jun 2009 14:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-301</guid>
		<description>[...] The xmlrpc.php file and site security (Wordpress) http://is.gd/1dA6r# [...]</description>
		<content:encoded><![CDATA[<p>[...] The xmlrpc.php file and site security (WordPress) <a href="http://is.gd/1dA6r#" rel="nofollow">http://is.gd/1dA6r#</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: (Anti) Social-Lists 6/28/09 &#124; (Anti) Social Development</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-296</link>
		<dc:creator>(Anti) Social-Lists 6/28/09 &#124; (Anti) Social Development</dc:creator>
		<pubDate>Sun, 28 Jun 2009 04:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-296</guid>
		<description>[...] Xmlrpc Php Security - If you&#8217;ve ever wondered what the xmlrpc.php file, in your WordPress installation, does, this article provides an explanation. You might also want to take a look into the upcoming WordPress book, Digging Into WordPress, written by Jeff Starr and Chris Coyier. [...]</description>
		<content:encoded><![CDATA[<p>[...] Xmlrpc Php Security &#8211; If you&#8217;ve ever wondered what the xmlrpc.php file, in your WordPress installation, does, this article provides an explanation. You might also want to take a look into the upcoming WordPress book, Digging Into WordPress, written by Jeff Starr and Chris Coyier. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Starr</title>
		<link>http://digwp.com/2009/06/xmlrpc-php-security/#comment-293</link>
		<dc:creator>Jeff Starr</dc:creator>
		<pubDate>Sun, 28 Jun 2009 01:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://diggingintowordpress.com/?p=169#comment-293</guid>
		<description>Awesome -- thanks for the feedback :)</description>
		<content:encoded><![CDATA[<p>Awesome &#8212; thanks for the feedback :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

