<?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: AskApache WordPress Hardening Plugin</title>
	<atom:link href="http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin</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: Philipp</title>
		<link>http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin/comment-page-1#comment-14218</link>
		<dc:creator>Philipp</dc:creator>
		<pubDate>Wed, 22 Oct 2008 15:53:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin/#comment-14218</guid>
		<description>From what&#039;s told within the linked Article you would need to put it into each folder as the directory tag is only allowed to be used within httpd.conf. You could mod for sure the current htaccess file so it doesn&#039;t block every php file like index.php if it would be within the root WP folder. Anyway this way here isn&#039;t the best one as AskApache suggested some time ago. It&#039;s better to proceed this way:
http://www.askapache.com/htaccess/htaccess-plugin-blocks-spam-hackers-and-password-protects-blog.html
as described under Protect wp-content &amp; wp-includes. This is only denying direct requests to these files, internal calls will still work.</description>
		<content:encoded><![CDATA[<p>From what&#8217;s told within the linked Article you would need to put it into each folder as the directory tag is only allowed to be used within httpd.conf. You could mod for sure the current htaccess file so it doesn&#8217;t block every php file like index.php if it would be within the root WP folder. Anyway this way here isn&#8217;t the best one as AskApache suggested some time ago. It&#8217;s better to proceed this way:<br />
<a href="http://www.askapache.com/htaccess/htaccess-plugin-blocks-spam-hackers-and-password-protects-blog.html" rel="nofollow">http://www.askapache.com/htaccess/htaccess-plugin-blocks-spam-hackers-and-password-protects-blog.html</a><br />
as described under Protect wp-content &#038; wp-includes. This is only denying direct requests to these files, internal calls will still work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: n00b</title>
		<link>http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin/comment-page-1#comment-14182</link>
		<dc:creator>n00b</dc:creator>
		<pubDate>Thu, 09 Oct 2008 22:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin/#comment-14182</guid>
		<description>Hi.
About: &quot;Restricting wpcontent
&amp; wpincludes&quot; do i need to put two copies of the .httacces file in each folder (wpcontent &amp; wpincludes) or just one in the top level directory ponting to both?
I just read .htacces files supercedes the .htacces file in the above directory.</description>
		<content:encoded><![CDATA[<p>Hi.<br />
About: &#8220;Restricting wpcontent<br />
&amp; wpincludes&#8221; do i need to put two copies of the .httacces file in each folder (wpcontent &amp; wpincludes) or just one in the top level directory ponting to both?<br />
I just read .htacces files supercedes the .htacces file in the above directory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hardening WordPress with .htaccess &#171; WordPress .htaccess</title>
		<link>http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin/comment-page-1#comment-12872</link>
		<dc:creator>Hardening WordPress with .htaccess &#171; WordPress .htaccess</dc:creator>
		<pubDate>Mon, 11 Aug 2008 16:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/askapache-wordpress-hardening-plugin/#comment-12872</guid>
		<description>[...] WordPress with&#160;.htaccess Filed under: htaccess, security &#8212; htaccess @ 4:56 pm       AskApache WordPress Hardening Plugin Filed Under (Plugin Reviews, WordPress) by DK on 7 August [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress with&nbsp;.htaccess Filed under: htaccess, security &#8212; htaccess @ 4:56 pm       AskApache WordPress Hardening Plugin Filed Under (Plugin Reviews, WordPress) by DK on 7 August [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

