<?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: Unobtrusive Antispam: Using JavaScript and Cookies Efficiently To Thwart Spammers and Hackers</title>
	<atom:link href="http://thecoffeedesk.com/news/index.php/2009/06/09/unobtrusive-antispam/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecoffeedesk.com/news/index.php/2009/06/09/unobtrusive-antispam/</link>
	<description>The Leader In Technical News and Commentary</description>
	<lastBuildDate>Sun, 11 Dec 2011 15:02:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: nomalab</title>
		<link>http://thecoffeedesk.com/news/index.php/2009/06/09/unobtrusive-antispam/comment-page-1/#comment-619</link>
		<dc:creator>nomalab</dc:creator>
		<pubDate>Wed, 08 Jul 2009 04:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://thecoffeedesk.com/news/?p=594#comment-619</guid>
		<description>Hi again, had to come back to this. Found something interesting: Honeypot CAPTCHA based on empty form field. Will need to test it but the concept is brilliantly simple.

http://haacked.com/archive/2007/09/11/honeypot-captcha.aspx</description>
		<content:encoded><![CDATA[<p>Hi again, had to come back to this. Found something interesting: Honeypot CAPTCHA based on empty form field. Will need to test it but the concept is brilliantly simple.</p>
<p><a href="http://haacked.com/archive/2007/09/11/honeypot-captcha.aspx" rel="nofollow">http://haacked.com/archive/2007/09/11/honeypot-captcha.aspx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony</title>
		<link>http://thecoffeedesk.com/news/index.php/2009/06/09/unobtrusive-antispam/comment-page-1/#comment-597</link>
		<dc:creator>Anthony</dc:creator>
		<pubDate>Thu, 18 Jun 2009 15:21:30 +0000</pubDate>
		<guid isPermaLink="false">http://thecoffeedesk.com/news/?p=594#comment-597</guid>
		<description>@nomalab that&#039;s very true. One simplistic way of circumventing this is to discreetly block the default cURL useragent (which is modifiable via the command line) and/or establishing a set amount of time between the request of the form and the processing on the server, to catch and thwart automation in general.

But nice catch, although the form randomization would thwart this unless a wget/parser combination is used in addition with the cURL method.

Thanks for the comment!</description>
		<content:encoded><![CDATA[<p>@nomalab that&#8217;s very true. One simplistic way of circumventing this is to discreetly block the default cURL useragent (which is modifiable via the command line) and/or establishing a set amount of time between the request of the form and the processing on the server, to catch and thwart automation in general.</p>
<p>But nice catch, although the form randomization would thwart this unless a wget/parser combination is used in addition with the cURL method.</p>
<p>Thanks for the comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nomalab</title>
		<link>http://thecoffeedesk.com/news/index.php/2009/06/09/unobtrusive-antispam/comment-page-1/#comment-596</link>
		<dc:creator>nomalab</dc:creator>
		<pubDate>Thu, 18 Jun 2009 15:09:52 +0000</pubDate>
		<guid isPermaLink="false">http://thecoffeedesk.com/news/?p=594#comment-596</guid>
		<description>About the cookie method: it&#039;s a no brainer to use cURL to get around this: first make a request to the form page to get the session ID in the cookie (CURLOPT_COOKIEFILE and CURLOPT_COOKIEJAR), then post past the form directly to the form handler using that cookie. So, requiring cookies will keep the script kiddies away, but won&#039;t stop people who know what they are doing.</description>
		<content:encoded><![CDATA[<p>About the cookie method: it&#8217;s a no brainer to use cURL to get around this: first make a request to the form page to get the session ID in the cookie (CURLOPT_COOKIEFILE and CURLOPT_COOKIEJAR), then post past the form directly to the form handler using that cookie. So, requiring cookies will keep the script kiddies away, but won&#8217;t stop people who know what they are doing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
