<?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: Keeping the bots out</title>
	<atom:link href="http://blogsecurity.net/wordpress/keeping-the-bots-out/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/keeping-the-bots-out</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: jidanni</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-16163</link>
		<dc:creator>jidanni</dc:creator>
		<pubDate>Fri, 20 Feb 2009 05:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-16163</guid>
		<description>I use WWWOFFLE, and libwww-perl&#039;s HEAD and GET, etc. to fetch and then
browse later offline all the time, even though I now have ADSL. So if
I&#039;m blocked from somebody&#039;s site, well, it&#039;s their loss.</description>
		<content:encoded><![CDATA[<p>I use WWWOFFLE, and libwww-perl&#8217;s HEAD and GET, etc. to fetch and then<br />
browse later offline all the time, even though I now have ADSL. So if<br />
I&#8217;m blocked from somebody&#8217;s site, well, it&#8217;s their loss.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Carrero Fdez-Baillo</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-2438</link>
		<dc:creator>David Carrero Fdez-Baillo</dc:creator>
		<pubDate>Thu, 18 Oct 2007 07:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-2438</guid>
		<description>I use modsecurity for all sites, and block many attacks :))</description>
		<content:encoded><![CDATA[<p>I use modsecurity for all sites, and block many attacks :))</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Haun</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-2077</link>
		<dc:creator>Dirk Haun</dc:creator>
		<pubDate>Sat, 13 Oct 2007 08:37:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-2077</guid>
		<description>As others have noted, a lot of the script kiddies do use the unmodified libwww-perl user agent string, so it does help a lot to simply block that.

Also, they often try these include tricks with each and every PHP script that takes a parameter. Just because they try doesn&#039;t mean an actual exploit exists for that script.</description>
		<content:encoded><![CDATA[<p>As others have noted, a lot of the script kiddies do use the unmodified libwww-perl user agent string, so it does help a lot to simply block that.</p>
<p>Also, they often try these include tricks with each and every PHP script that takes a parameter. Just because they try doesn&#8217;t mean an actual exploit exists for that script.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-2036</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Fri, 12 Oct 2007 18:40:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-2036</guid>
		<description>Abel, David, 
My guess would be, that unless there&#039;s a top-secret 0day out there ;) It&#039;s more likely that some script-kiddy didn&#039;t get what the vulnerability is, and therefore is pointless trying to include.</description>
		<content:encoded><![CDATA[<p>Abel, David,<br />
My guess would be, that unless there&#8217;s a top-secret 0day out there ;) It&#8217;s more likely that some script-kiddy didn&#8217;t get what the vulnerability is, and therefore is pointless trying to include.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-2024</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Fri, 12 Oct 2007 11:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-2024</guid>
		<description>Abel, yes I know of the wp-pass redirect vulnerability that Adrian released on BlogSec a couple months back; however, the vulnerability they are trying to exploit here is a remote file include bug.</description>
		<content:encoded><![CDATA[<p>Abel, yes I know of the wp-pass redirect vulnerability that Adrian released on BlogSec a couple months back; however, the vulnerability they are trying to exploit here is a remote file include bug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abel Cheung</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-2022</link>
		<dc:creator>Abel Cheung</dc:creator>
		<pubDate>Fri, 12 Oct 2007 10:37:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-2022</guid>
		<description>You&#039;re asking what&#039;s that wp-pass thing? Interesting to see that you forgot &lt;a href=&quot;http://blogsecurity.net/news/news-050707/&quot; rel=&quot;nofollow&quot;&gt;your own post&lt;/a&gt; 3 months ago. :-D

About user-agent, I think Donncha actually got a point. From statistics of my own site, the user-agent from spam messages surprisingly concentrates on just a few choices (though most of them have null user-agent string). Not the ultimate solution, but can still block a noticable portion of the spam messages.</description>
		<content:encoded><![CDATA[<p>You&#8217;re asking what&#8217;s that wp-pass thing? Interesting to see that you forgot <a href="http://blogsecurity.net/news/news-050707/" rel="nofollow">your own post</a> 3 months ago. :-D</p>
<p>About user-agent, I think Donncha actually got a point. From statistics of my own site, the user-agent from spam messages surprisingly concentrates on just a few choices (though most of them have null user-agent string). Not the ultimate solution, but can still block a noticable portion of the spam messages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James McKay</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-1978</link>
		<dc:creator>James McKay</dc:creator>
		<pubDate>Thu, 11 Oct 2007 21:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-1978</guid>
		<description>I saw Donncha&#039;s post and I think you&#039;ve missed the point of it somewhat. The point wasn&#039;t to eliminate all the nasties altogether -- you will need to rely on other solutions for that -- but reduce the load on your server. The traffic that it blocks is all coming from bots, which are churning out requests by the millions to try and cause as widespread damage as they can.

This technique may not stop all bot attacks, but it is not entirely useless.

Your point about RSS aggregation agents may be valid however, though do any really legitimate ones actually use the libwww-perl user agent, or is that more the domain of splogs and things, as I would have thought to be the case? In any case, if there are some legitimate LWP aggregators out there, I&#039;m sure it must be possible to come up with some .htaccess rules that allow them access to your RSS feeds while denying  them everything else.</description>
		<content:encoded><![CDATA[<p>I saw Donncha&#8217;s post and I think you&#8217;ve missed the point of it somewhat. The point wasn&#8217;t to eliminate all the nasties altogether &#8212; you will need to rely on other solutions for that &#8212; but reduce the load on your server. The traffic that it blocks is all coming from bots, which are churning out requests by the millions to try and cause as widespread damage as they can.</p>
<p>This technique may not stop all bot attacks, but it is not entirely useless.</p>
<p>Your point about RSS aggregation agents may be valid however, though do any really legitimate ones actually use the libwww-perl user agent, or is that more the domain of splogs and things, as I would have thought to be the case? In any case, if there are some legitimate LWP aggregators out there, I&#8217;m sure it must be possible to come up with some .htaccess rules that allow them access to your RSS feeds while denying  them everything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth Heyes</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-1977</link>
		<dc:creator>Gareth Heyes</dc:creator>
		<pubDate>Thu, 11 Oct 2007 21:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-1977</guid>
		<description>Our new WPIDS will protect against these attacks :)

They are generic scans against PHP code and not based on any Wordpress code, I get these a lot.</description>
		<content:encoded><![CDATA[<p>Our new WPIDS will protect against these attacks :)</p>
<p>They are generic scans against PHP code and not based on any Wordpress code, I get these a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donncha O Caoimh</title>
		<link>http://blogsecurity.net/wordpress/keeping-the-bots-out/comment-page-1#comment-1976</link>
		<dc:creator>Donncha O Caoimh</dc:creator>
		<pubDate>Thu, 11 Oct 2007 21:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/keeping-the-bots-out/#comment-1976</guid>
		<description>I beg to differ. Even though it&#039;s trivial to change the UA they obviously haven&#039;t. I&#039;m certainly not the first to urge for blocking libwww which means the exploit authors either don&#039;t use Google, or realise only a small number of sites actually block the UA.

Looking forward to the modsecurity post!</description>
		<content:encoded><![CDATA[<p>I beg to differ. Even though it&#8217;s trivial to change the UA they obviously haven&#8217;t. I&#8217;m certainly not the first to urge for blocking libwww which means the exploit authors either don&#8217;t use Google, or realise only a small number of sites actually block the UA.</p>
<p>Looking forward to the modsecurity post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
