<?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 Hardening Project Update</title>
	<atom:link href="http://blogsecurity.net/wordpress/wordpress-hardening-project-update/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BlogSecurity &#187; Blog Archive &#187; WPIDS - WordPress Intruder Detection System</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-5343</link>
		<dc:creator>BlogSecurity &#187; Blog Archive &#187; WPIDS - WordPress Intruder Detection System</dc:creator>
		<pubDate>Thu, 22 Nov 2007 03:00:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-5343</guid>
		<description>[...] so on. In short, its a defense plugin for WordPress that BlogSec members have been working on for a few months now. I would say it was more of an Intruder Prevention System then an Intruder Detection [...]</description>
		<content:encoded><![CDATA[<p>[...] so on. In short, its a defense plugin for WordPress that BlogSec members have been working on for a few months now. I would say it was more of an Intruder Prevention System then an Intruder Detection [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-2300</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Wed, 17 Oct 2007 03:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-2300</guid>
		<description>This is a really nice, well-thought-out effort, but not a best-practice...

The BEST way to block all of these files is to only block EXTERNAL requests for them.  IOW, if your wp-cache requests a file, it should be allowed.  If a visitor on your webpage requests the same file, it should be denied.  This seems impossible to accomplish but actually mod_rewrite provides a really cool way...

for example, this blocks all external requests (except those generated by ErrorDocument code /index.php?error=code) for files ending in .php in either the wp-includes or wp-content directory, but it doesn&#039;t block your server or WP install!
&lt;code&gt;
RewriteCond %{QUERY_STRING} !error
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /(wp-includes&#124;wp-content)/(.+)\.php\ HTTP/
RewriteRule .* - [F]
&lt;/code&gt;


code from &lt;a href=&quot;http://www.askapache.com/htaccess/apache-htaccess.html&quot; rel=&quot;nofollow&quot;&gt;htaccess tutorial&lt;/a&gt; 

Another way to secure your wordpress with .htaccess is by using my wordpress plugin: &lt;a href=&quot;http://www.askapache.com/wordpress/htaccess-password-protect.html&quot; rel=&quot;nofollow&quot;&gt;htaccess password protect&lt;/a&gt; on AskApache.com</description>
		<content:encoded><![CDATA[<p>This is a really nice, well-thought-out effort, but not a best-practice&#8230;</p>
<p>The BEST way to block all of these files is to only block EXTERNAL requests for them.  IOW, if your wp-cache requests a file, it should be allowed.  If a visitor on your webpage requests the same file, it should be denied.  This seems impossible to accomplish but actually mod_rewrite provides a really cool way&#8230;</p>
<p>for example, this blocks all external requests (except those generated by ErrorDocument code /index.php?error=code) for files ending in .php in either the wp-includes or wp-content directory, but it doesn&#8217;t block your server or WP install!<br />
<code><br />
RewriteCond %{QUERY_STRING} !error<br />
RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /(wp-includes|wp-content)/(.+)\.php\ HTTP/<br />
RewriteRule .* - [F]<br />
</code></p>
<p>code from <a href="http://www.askapache.com/htaccess/apache-htaccess.html" rel="nofollow">htaccess tutorial</a> </p>
<p>Another way to secure your wordpress with .htaccess is by using my wordpress plugin: <a href="http://www.askapache.com/wordpress/htaccess-password-protect.html" rel="nofollow">htaccess password protect</a> on AskApache.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BlogSecurity &#187; Inspector WordPress Plugin Review</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1720</link>
		<dc:creator>BlogSecurity &#187; Inspector WordPress Plugin Review</dc:creator>
		<pubDate>Mon, 08 Oct 2007 06:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1720</guid>
		<description>[...] The plugin has a list of security conditions (stored in conditions.txt). These rules define what requests are considered bad. I took interest in the plugin to see if we could use it in the WP hardening project. [...]</description>
		<content:encoded><![CDATA[<p>[...] The plugin has a list of security conditions (stored in conditions.txt). These rules define what requests are considered bad. I took interest in the plugin to see if we could use it in the WP hardening project. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1266</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Mon, 24 Sep 2007 15:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1266</guid>
		<description>Mutt, great to hear, thanks for your feedback!</description>
		<content:encoded><![CDATA[<p>Mutt, great to hear, thanks for your feedback!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mutt</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1264</link>
		<dc:creator>Mutt</dc:creator>
		<pubDate>Mon, 24 Sep 2007 15:02:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1264</guid>
		<description>I&#039;ve been testing Gareth&#039;s WP-Lockdown.  Seems to work well for me with most of the bugs now ironed out.  I look forward to developments here.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been testing Gareth&#8217;s WP-Lockdown.  Seems to work well for me with most of the bugs now ironed out.  I look forward to developments here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ReZEN</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1204</link>
		<dc:creator>ReZEN</dc:creator>
		<pubDate>Fri, 21 Sep 2007 11:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1204</guid>
		<description>I wrote a personal plugin encryptconf wich encrypts the wordpress configuration file.  Might want to give it a look:  http://www.rezen.org/encryptconf.zip</description>
		<content:encoded><![CDATA[<p>I wrote a personal plugin encryptconf wich encrypts the wordpress configuration file.  Might want to give it a look:  <a href="http://www.rezen.org/encryptconf.zip" rel="nofollow">http://www.rezen.org/encryptconf.zip</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress Hardening Project &#171; Among the Impostors - Cyber Fraud</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1157</link>
		<dc:creator>Wordpress Hardening Project &#171; Among the Impostors - Cyber Fraud</dc:creator>
		<pubDate>Tue, 18 Sep 2007 11:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1157</guid>
		<description>[...] Wordpress Hardening&#160;Project  David Kierznowski of Gnucitizen and Philipp Heinze  have been working on a WordPress lock down toold , wp-lockdows, to help make the blogging world a safer place. You can find more on this, and the plugin wp-ids over at the WordPress Blog . [...]</description>
		<content:encoded><![CDATA[<p>[...] Wordpress Hardening&nbsp;Project  David Kierznowski of Gnucitizen and Philipp Heinze  have been working on a WordPress lock down toold , wp-lockdows, to help make the blogging world a safer place. You can find more on this, and the plugin wp-ids over at the WordPress Blog . [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Irizarry</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1142</link>
		<dc:creator>Robert Irizarry</dc:creator>
		<pubDate>Mon, 17 Sep 2007 17:57:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1142</guid>
		<description>I&#039;m really looking forward to this plugin and I&#039;m sure folks will appreciate an easy to harden their WordPress environments. Thanks in advance!</description>
		<content:encoded><![CDATA[<p>I&#8217;m really looking forward to this plugin and I&#8217;m sure folks will appreciate an easy to harden their WordPress environments. Thanks in advance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomsn</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1138</link>
		<dc:creator>Tomsn</dc:creator>
		<pubDate>Mon, 17 Sep 2007 17:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1138</guid>
		<description>One Question: why does the WP Developers not add some hardening things like the output text of the wrong Username or Password...
Every changes i made it&#039;s had it even a new update comes... :-(</description>
		<content:encoded><![CDATA[<p>One Question: why does the WP Developers not add some hardening things like the output text of the wrong Username or Password&#8230;<br />
Every changes i made it&#8217;s had it even a new update comes&#8230; :-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SigT</title>
		<link>http://blogsecurity.net/wordpress/wordpress-hardening-project-update/comment-page-1#comment-1135</link>
		<dc:creator>SigT</dc:creator>
		<pubDate>Mon, 17 Sep 2007 13:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wordpress-hardening-project-update/#comment-1135</guid>
		<description>&lt;strong&gt;WPIDS y el WordPress Hardening Project...&lt;/strong&gt;

WPIDS es un port de PHPIDS a WordPress, si no me equivoco la traducción vendría a ser Sistema de Detección de Intrusiones para WordPress (WordPress Intrusion Detection System) ya que aunque no aclaran el término, IDS se refiere a esto.

Según una ...</description>
		<content:encoded><![CDATA[<p><strong>WPIDS y el WordPress Hardening Project&#8230;</strong></p>
<p>WPIDS es un port de PHPIDS a WordPress, si no me equivoco la traducción vendría a ser Sistema de Detección de Intrusiones para WordPress (WordPress Intrusion Detection System) ya que aunque no aclaran el término, IDS se refiere a esto.</p>
<p>Según una &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

