<?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: &#8220;Hiding&#8221; WordPress installation files</title>
	<atom:link href="http://ox.no/posts/hiding-wordpress-installation-files/feed" rel="self" type="application/rss+xml" />
	<link>http://ox.no/posts/hiding-wordpress-installation-files</link>
	<description>Håvard Stranden&#039;s website</description>
	<lastBuildDate>Thu, 29 Mar 2012 00:08:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Secure your WordPress website &#171; Digital Intersect :: Your knowledgebank to Open Source Framework and Web Design trends</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-1636</link>
		<dc:creator>Secure your WordPress website &#171; Digital Intersect :: Your knowledgebank to Open Source Framework and Web Design trends</dc:creator>
		<pubDate>Thu, 09 Jun 2011 13:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-1636</guid>
		<description>&lt;p&gt;[...] Don’t allow hackers to find your WordPress, hide them.  Here’s a simple trick to help hide WordPress files to the public: http://ox.no/posts/hiding-wordpress-installation-files [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Don’t allow hackers to find your WordPress, hide them.  Here’s a simple trick to help hide WordPress files to the public: <a href="http://ox.no/posts/hiding-wordpress-installation-files" rel="nofollow">http://ox.no/posts/hiding-wordpress-installation-files</a> [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: 10 things to know about WordPress security &#124; Abdee</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-1377</link>
		<dc:creator>10 things to know about WordPress security &#124; Abdee</dc:creator>
		<pubDate>Tue, 26 Apr 2011 04:38:29 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-1377</guid>
		<description>&lt;p&gt;[...] Don’t allow hackers to find your WordPress, hide them. Here’s a simple trick to help hide WordPress files to the public: http://ox.no/posts/hiding-wordpress-installation-files [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Don’t allow hackers to find your WordPress, hide them. Here’s a simple trick to help hide WordPress files to the public: <a href="http://ox.no/posts/hiding-wordpress-installation-files" rel="nofollow">http://ox.no/posts/hiding-wordpress-installation-files</a> [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: 10 Things to know about WordPress Security &#124; Room 3064</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-1361</link>
		<dc:creator>10 Things to know about WordPress Security &#124; Room 3064</dc:creator>
		<pubDate>Thu, 31 Mar 2011 04:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-1361</guid>
		<description>&lt;p&gt;[...] Don&#8217;t allow hackers to find your WordPress, hide them.  Here&#8217;s a simple trick to help hide WordPress files to the public: http://ox.no/posts/hiding-wordpress-installation-files [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Don&#8217;t allow hackers to find your WordPress, hide them.  Here&#8217;s a simple trick to help hide WordPress files to the public: <a href="http://ox.no/posts/hiding-wordpress-installation-files" rel="nofollow">http://ox.no/posts/hiding-wordpress-installation-files</a> [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Installation Techniques &#124; Guide for Blogs and Wordpress</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-487</link>
		<dc:creator>WordPress Installation Techniques &#124; Guide for Blogs and Wordpress</dc:creator>
		<pubDate>Mon, 13 Oct 2008 06:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-487</guid>
		<description>&lt;p&gt;[...] &#8220;Hiding&#8221; WordPress Installation Files (offsite) [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Hiding&#8221; WordPress Installation Files (offsite) [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-448</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Tue, 29 Apr 2008 04:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-448</guid>
		<description>&lt;p&gt;OH! Well then that makes perfect sense, I was reading too much into it.&lt;/p&gt;

&lt;p&gt;Sorry about posting a link to &lt;em&gt;[ad removed]&lt;/em&gt; in response to your suggestion I contact WP support for &quot;help&quot;.  Sorry for spamming your thread bro.&lt;/p&gt;

&lt;p&gt;~Out&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>OH! Well then that makes perfect sense, I was reading too much into it.</p>

<p>Sorry about posting a link to <em>[ad removed]</em> in response to your suggestion I contact WP support for &#8220;help&#8221;.  Sorry for spamming your thread bro.</p>

<p>~Out</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Håvard</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-447</link>
		<dc:creator>Håvard</dc:creator>
		<pubDate>Sun, 27 Apr 2008 23:24:40 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-447</guid>
		<description>&lt;p&gt;No. The article describes a technique for &quot;hiding&quot; your Wordpress installation from public access, which obviously requires a working Wordpress installation.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>No. The article describes a technique for &#8220;hiding&#8221; your WordPress installation from public access, which obviously requires a working WordPress installation.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-446</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Sun, 27 Apr 2008 23:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-446</guid>
		<description>&lt;p&gt;&lt;em&gt;Edit: Removed yet another ad from this guy    -H&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I&#039;m still not seeing what this actually does.  So you are saying that these rules should only be put in place BEFORE you actually install wordpress?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><em>Edit: Removed yet another ad from this guy    -H</em></p>

<p>I&#8217;m still not seeing what this actually does.  So you are saying that these rules should only be put in place BEFORE you actually install wordpress?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Håvard</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-442</link>
		<dc:creator>Håvard</dc:creator>
		<pubDate>Sun, 27 Apr 2008 13:08:50 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-442</guid>
		<description>&lt;p&gt;AskApache: What the article does is to add a few lines before &lt;em&gt;the default Wordpress rewrite rules&lt;/em&gt;. &lt;/p&gt;

&lt;p&gt;The added lines state that if the request is for a file in the wordpress directory (which can/must be changed if the directory does not match your installation), and the referer is not the site (which can/must also be changed to match your installation), then the request is redirected to the root of the site (which can/must also be changed to match your preference and installation). &lt;/p&gt;

&lt;p&gt;The remaining ruleset is &lt;em&gt;the Wordpress default&lt;/em&gt;, which is the same in any Wordpress installation which manages &lt;code&gt;.htaccess&lt;/code&gt;. Reading the ruleset, you can see that it lets each request through for handling by index.php, unless the request is for an actual directory or file. I suggest you read the Wordpress documentation on permalinks and read the parts of Wordpress that handle permalinks (i.e. index.php and referred functions) for a detailed explanation. &lt;/p&gt;

&lt;p&gt;If you have issues with the default ruleset, I suggest you contact the Wordpress development team.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>AskApache: What the article does is to add a few lines before <em>the default WordPress rewrite rules</em>. </p>

<p>The added lines state that if the request is for a file in the wordpress directory (which can/must be changed if the directory does not match your installation), and the referer is not the site (which can/must also be changed to match your installation), then the request is redirected to the root of the site (which can/must also be changed to match your preference and installation). </p>

<p>The remaining ruleset is <em>the WordPress default</em>, which is the same in any WordPress installation which manages <code>.htaccess</code>. Reading the ruleset, you can see that it lets each request through for handling by index.php, unless the request is for an actual directory or file. I suggest you read the WordPress documentation on permalinks and read the parts of WordPress that handle permalinks (i.e. index.php and referred functions) for a detailed explanation. </p>

<p>If you have issues with the default ruleset, I suggest you contact the WordPress development team.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-441</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Sat, 26 Apr 2008 17:03:16 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-441</guid>
		<description>&lt;p&gt;Havard,&lt;/p&gt;

&lt;p&gt;Ya interesting discussion.  I would like for you to explain where I was incorrect in my assessment of the negative SEO aspect.  Let me simplify my objections so you can better explain.&lt;/p&gt;

&lt;p&gt;Basically, Googlebot finds a link to &lt;a&gt;Hiding wordpress installation files&lt;/a&gt; in the comments section of the &lt;a&gt;AskApache Password Protect&lt;/a&gt; plugin page, so then Googlebot, which has to act in accordance with the RFC HTTP client specifications just like any user-agent/browser, makes a GET request for this page with the referral header being set as the askapache.com plugin page.&lt;/p&gt;

&lt;p&gt;If I understand, this code would then issue a 301 Permanent redirect to Googlebot instructing it to go to your blogs home page instead.  When Googlebot or other search engine robots receive a 301 permanent redirect they usually take the redirecting URL OUT of their search index.&lt;/p&gt;

&lt;p&gt;But once googlebot was on your homepage, any links to your site that it followed from there  WOULD be allowed because googlebot would then set the referall header to your site.&lt;/p&gt;

&lt;p&gt;When Googlebot receives a 301 redirect like this, it actually transfers some of the &lt;a&gt;page-rank&lt;/a&gt; associated with the page issusing the redirect, to the page it is being redirected to.  So this could actually boost the page-rank of your home-page, its a tricky thing.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Havard,</p>

<p>Ya interesting discussion.  I would like for you to explain where I was incorrect in my assessment of the negative SEO aspect.  Let me simplify my objections so you can better explain.</p>

<p>Basically, Googlebot finds a link to <a>Hiding wordpress installation files</a> in the comments section of the <a>AskApache Password Protect</a> plugin page, so then Googlebot, which has to act in accordance with the RFC HTTP client specifications just like any user-agent/browser, makes a GET request for this page with the referral header being set as the askapache.com plugin page.</p>

<p>If I understand, this code would then issue a 301 Permanent redirect to Googlebot instructing it to go to your blogs home page instead.  When Googlebot or other search engine robots receive a 301 permanent redirect they usually take the redirecting URL OUT of their search index.</p>

<p>But once googlebot was on your homepage, any links to your site that it followed from there  WOULD be allowed because googlebot would then set the referall header to your site.</p>

<p>When Googlebot receives a 301 redirect like this, it actually transfers some of the <a>page-rank</a> associated with the page issusing the redirect, to the page it is being redirected to.  So this could actually boost the page-rank of your home-page, its a tricky thing.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Håvard</title>
		<link>http://ox.no/posts/hiding-wordpress-installation-files/comment-page-1#comment-432</link>
		<dc:creator>Håvard</dc:creator>
		<pubDate>Mon, 21 Apr 2008 07:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://ox.no/posts/hiding-wordpress-installation-files#comment-432</guid>
		<description>&lt;p&gt;&lt;&lt;/p&gt;

&lt;p&gt;p&gt;&lt;/p&gt;

&lt;p&gt;AskApache: Again, your claim that the &quot;hiding&quot; technique has negative effects on SEO are false. The article simply extends the Wordpress rewrite rules.&lt;/p&gt;

&lt;p&gt;Other than that, your reasoning about the article is mostly correct.&lt;/p&gt;

&lt;p&gt;Your reasoning about the security challenges with your own plugin, however, are faulty. If someone wants to bypass HTTP Basic authentication over an insecure transport, they will be able to do so. Without a secure transport, the authentication cannot be trusted.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&lt;</p>

<p>p></p>

<p>AskApache: Again, your claim that the &#8220;hiding&#8221; technique has negative effects on SEO are false. The article simply extends the WordPress rewrite rules.</p>

<p>Other than that, your reasoning about the article is mostly correct.</p>

<p>Your reasoning about the security challenges with your own plugin, however, are faulty. If someone wants to bypass HTTP Basic authentication over an insecure transport, they will be able to do so. Without a secure transport, the authentication cannot be trusted.</p>]]></content:encoded>
	</item>
</channel>
</rss>

