<?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: Brute Force Attack Hitting WordPress</title>
	<atom:link href="http://wpblogger.com/wordpress-brute-force-attack.php/feed" rel="self" type="application/rss+xml" />
	<link>http://wpblogger.com/wordpress-brute-force-attack.php</link>
	<description>All things WordPress</description>
	<lastBuildDate>Tue, 07 Sep 2010 14:53:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Sebastian</title>
		<link>http://wpblogger.com/wordpress-brute-force-attack.php#comment-1307</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Mon, 30 Nov 2009 23:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://wpblogger.com/?p=375#comment-1307</guid>
		<description>Ben, you can use LIMIT (requiring a valid usr:pw for access to wp-admin) from any place. In addition, you can make use of a somewhat unique and not that guessable GET variable to restrict access to the wp-admin directory. Or, just use a proxy ... there are so many solutions.</description>
		<content:encoded><![CDATA[<p>Ben, you can use LIMIT (requiring a valid usr:pw for access to wp-admin) from any place. In addition, you can make use of a somewhat unique and not that guessable GET variable to restrict access to the wp-admin directory. Or, just use a proxy &#8230; there are so many solutions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan  Beale</title>
		<link>http://wpblogger.com/wordpress-brute-force-attack.php#comment-1306</link>
		<dc:creator>Ryan  Beale</dc:creator>
		<pubDate>Mon, 30 Nov 2009 23:07:22 +0000</pubDate>
		<guid isPermaLink="false">http://wpblogger.com/?p=375#comment-1306</guid>
		<description>Cool.  Thanks again!</description>
		<content:encoded><![CDATA[<p>Cool.  Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Cook</title>
		<link>http://wpblogger.com/wordpress-brute-force-attack.php#comment-1305</link>
		<dc:creator>Ben Cook</dc:creator>
		<pubDate>Mon, 30 Nov 2009 23:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://wpblogger.com/?p=375#comment-1305</guid>
		<description>Ryan, from what I&#039;ve read that should safeguard you from this specific threat. I&#039;m not sure how widespread it is just yet but when a script is released into the wild like that, there tend to be plenty of people willing to give it a try.</description>
		<content:encoded><![CDATA[<p>Ryan, from what I&#8217;ve read that should safeguard you from this specific threat. I&#8217;m not sure how widespread it is just yet but when a script is released into the wild like that, there tend to be plenty of people willing to give it a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan  Beale</title>
		<link>http://wpblogger.com/wordpress-brute-force-attack.php#comment-1304</link>
		<dc:creator>Ryan  Beale</dc:creator>
		<pubDate>Mon, 30 Nov 2009 22:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://wpblogger.com/?p=375#comment-1304</guid>
		<description>Thanks for the heads-up.  I use the Login Lockdown plugin and changed the admin user name to a new one.  Hopefully, that will be enough to fend off the attack</description>
		<content:encoded><![CDATA[<p>Thanks for the heads-up.  I use the Login Lockdown plugin and changed the admin user name to a new one.  Hopefully, that will be enough to fend off the attack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Cook</title>
		<link>http://wpblogger.com/wordpress-brute-force-attack.php#comment-1303</link>
		<dc:creator>Ben Cook</dc:creator>
		<pubDate>Mon, 30 Nov 2009 22:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://wpblogger.com/?p=375#comment-1303</guid>
		<description>Sebastian, yeah, that would be a very good solution for bloggers who do most of their blogging from one place.

Unfortunately, I log in to work on my sites from all sorts of places including plenty of networks via my iphone so that solution wouldn&#039;t work well for me.</description>
		<content:encoded><![CDATA[<p>Sebastian, yeah, that would be a very good solution for bloggers who do most of their blogging from one place.</p>
<p>Unfortunately, I log in to work on my sites from all sorts of places including plenty of networks via my iphone so that solution wouldn&#8217;t work well for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian</title>
		<link>http://wpblogger.com/wordpress-brute-force-attack.php#comment-1301</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Mon, 30 Nov 2009 21:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://wpblogger.com/?p=375#comment-1301</guid>
		<description>Also: .htaccess  and .htpasswd are your friends.


    Order Deny,Allow
    Deny from all
    Allow from your_ip_addy


.htaccess in wp-admin:

AuthUserFile /out_of_reach_for_web_server/.htpasswd
AuthGroupFile /dev/null
AuthName &quot;GFY&quot;
AuthType Basic


require valid-user


http://httpd.apache.org/docs/1.3/programs/htpasswd.html</description>
		<content:encoded><![CDATA[<p>Also: .htaccess  and .htpasswd are your friends.</p>
<p>    Order Deny,Allow<br />
    Deny from all<br />
    Allow from your_ip_addy</p>
<p>.htaccess in wp-admin:</p>
<p>AuthUserFile /out_of_reach_for_web_server/.htpasswd<br />
AuthGroupFile /dev/null<br />
AuthName &#8220;GFY&#8221;<br />
AuthType Basic</p>
<p>require valid-user</p>
<p><a href="http://httpd.apache.org/docs/1.3/programs/htpasswd.html">http://httpd.apache.org/docs/1.3/programs/htpasswd.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
