<?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: Firming up WordPress&#8217;s security</title>
	<atom:link href="http://atastypixel.com/blog/firming-up-wordpresss-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://atastypixel.com/blog/firming-up-wordpresss-security/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 00:47:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Ben</title>
		<link>http://atastypixel.com/blog/firming-up-wordpresss-security/comment-page-1/#comment-1179</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sun, 28 Jun 2009 17:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://atastypixel.com/blog/2009/05/10/firming-up-wordpresss-security/#comment-1179</guid>
		<description>&lt;p&gt;Hi! I&#039;m using your wordpress template - hope that is ok?
Those code-blocks you have in this post...is that the &quot;quote&quot; function?
Cause in my wordpress the quote-function is not showing a frame with another color like yours is doing here... (sorry for my bad english)&lt;/p&gt;

&lt;p&gt;Best greetings
Ben&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi! I&#8217;m using your wordpress template &#8211; hope that is ok?
Those code-blocks you have in this post&#8230;is that the &#8220;quote&#8221; function?
Cause in my wordpress the quote-function is not showing a frame with another color like yours is doing here&#8230; (sorry for my bad english)</p>

<p>Best greetings
Ben</p>]]></content:encoded>
	</item>
	<item>
		<title>By: aquariumfish</title>
		<link>http://atastypixel.com/blog/firming-up-wordpresss-security/comment-page-1/#comment-1104</link>
		<dc:creator>aquariumfish</dc:creator>
		<pubDate>Mon, 25 May 2009 02:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://atastypixel.com/blog/2009/05/10/firming-up-wordpresss-security/#comment-1104</guid>
		<description>&lt;p&gt;Hmm, I never took into concideration that if you limit your whole wp-admin directory to be accessed by just one IP Address that it may effects PING BACKS reading your comments above. Also I just read other issues it can cause also.

Read this thread here: http://bad-neighborhood.blogsblogsblogs.com/2007/08/29/login-lockdown-a-new-wordpress-security-plugin/&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hmm, I never took into concideration that if you limit your whole wp-admin directory to be accessed by just one IP Address that it may effects PING BACKS reading your comments above. Also I just read other issues it can cause also.

Read this thread here: <a href="http://bad-neighborhood.blogsblogsblogs.com/2007/08/29/login-lockdown-a-new-wordpress-security-plugin/" rel="nofollow">http://bad-neighborhood.blogsblogsblogs.com/2007/08/29/login-lockdown-a-new-wordpress-security-plugin/</a></p>]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://atastypixel.com/blog/firming-up-wordpresss-security/comment-page-1/#comment-1102</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 25 May 2009 01:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://atastypixel.com/blog/2009/05/10/firming-up-wordpresss-security/#comment-1102</guid>
		<description>&lt;p&gt;Good comments!
It&apos;s worth noting that, for those who don&apos;t have a fixed IP address (like me, for better or worse), this will require regular updating to match your current IP.&lt;/p&gt;

&lt;p&gt;It may be worth also limiting access to wp-login.php and possibly the xmlrpc.php RPC entry point, if one&apos;s feeling particularly paranoid - that can be done using the &apos;Files&apos; directive, with the same stuff from aquariumfish above.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Good comments!
It&apos;s worth noting that, for those who don&apos;t have a fixed IP address (like me, for better or worse), this will require regular updating to match your current IP.</p>

<p>It may be worth also limiting access to wp-login.php and possibly the xmlrpc.php RPC entry point, if one&apos;s feeling particularly paranoid &#8211; that can be done using the &apos;Files&apos; directive, with the same stuff from aquariumfish above.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: aquariumfish</title>
		<link>http://atastypixel.com/blog/firming-up-wordpresss-security/comment-page-1/#comment-1101</link>
		<dc:creator>aquariumfish</dc:creator>
		<pubDate>Mon, 25 May 2009 00:59:49 +0000</pubDate>
		<guid isPermaLink="false">http://atastypixel.com/blog/2009/05/10/firming-up-wordpresss-security/#comment-1101</guid>
		<description>&lt;p&gt;I&#039;ve added some breaks in to display the code hopefully better for you.&lt;/p&gt;

&lt;p&gt;Goes in .htaccess file dropped in wp-admin folder&lt;/p&gt;

&lt;p&gt;Order Deny,Allow&lt;br/&gt;
Deny from all&lt;br/&gt;
Allow from 92.239.86.166&lt;/p&gt;

&lt;p&gt;Add to your wordpress .htaccess file at the top to protect your wp-config file&lt;/p&gt;

&lt;p&gt;&lt;Files wp-config.php&gt;&lt;br/&gt;
Order Deny,Allow&lt;br/&gt;
Deny from All&lt;br/&gt;
&lt;/Files&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve added some breaks in to display the code hopefully better for you.</p>

<p>Goes in .htaccess file dropped in wp-admin folder</p>

<p>Order Deny,Allow<br />
Deny from all<br />
Allow from 92.239.86.166</p>

<p>Add to your wordpress .htaccess file at the top to protect your wp-config file</p>

<p>&lt;Files wp-config.php&gt;<br />
Order Deny,Allow<br />
Deny from All<br />
&lt;/Files&gt;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: aquariumfish</title>
		<link>http://atastypixel.com/blog/firming-up-wordpresss-security/comment-page-1/#comment-1100</link>
		<dc:creator>aquariumfish</dc:creator>
		<pubDate>Mon, 25 May 2009 00:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://atastypixel.com/blog/2009/05/10/firming-up-wordpresss-security/#comment-1100</guid>
		<description>&lt;p&gt;To be honest your making hard work of things, why don&#039;t you just drop a new .htaccess file in your wp-admin directory that only allows access to that folder and all files within it from one IP Address only (yours). To do that use this code (change the IP of course) to suit yours&lt;/p&gt;

&lt;p&gt;Order Deny,Allow&lt;br/&gt;
Deny from all&lt;br/&gt;
Allow from 11.111.11.111&lt;/p&gt;

&lt;p&gt;Robots don&#039;t need to index anything in your wp-admin folder, so you have no worries about them being blocked also. However, also add an entry in your robots.txt file to disallow all robots from wp-admin folder for better SEO and to tell robots not to bother anyway trying to gain access there like Google, Yahoo, MSN etc.&lt;/p&gt;

&lt;p&gt;Now you will have better SEO and only you alone will be allowed access not only to your admin login page, but the whole wp-admin directory.&lt;/p&gt;

&lt;p&gt;You should also block all access to your wp-config.php file also, again add this to your .htaccess file in your ROOT directory were you config file resides that conatins your wordpress code in it also.&lt;/p&gt;

&lt;p&gt;&lt;Files wp-config.php&gt;&lt;br/&gt;
Order Deny,Allow&lt;br/&gt;
Deny from All&lt;br/&gt;
&lt;/Files&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>To be honest your making hard work of things, why don&#8217;t you just drop a new .htaccess file in your wp-admin directory that only allows access to that folder and all files within it from one IP Address only (yours). To do that use this code (change the IP of course) to suit yours</p>

<p>Order Deny,Allow<br />
Deny from all<br />
Allow from 11.111.11.111</p>

<p>Robots don&#8217;t need to index anything in your wp-admin folder, so you have no worries about them being blocked also. However, also add an entry in your robots.txt file to disallow all robots from wp-admin folder for better SEO and to tell robots not to bother anyway trying to gain access there like Google, Yahoo, MSN etc.</p>

<p>Now you will have better SEO and only you alone will be allowed access not only to your admin login page, but the whole wp-admin directory.</p>

<p>You should also block all access to your wp-config.php file also, again add this to your .htaccess file in your ROOT directory were you config file resides that conatins your wordpress code in it also.</p>

<p>&lt;Files wp-config.php&gt;<br />
Order Deny,Allow<br />
Deny from All<br />
&lt;/Files&gt;</p>]]></content:encoded>
	</item>
</channel>
</rss>

