<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ads Captcha &#187; cracking gmail registration</title>
	<atom:link href="http://adscaptcha.com/tag/cracking-gmail-registration/feed/" rel="self" type="application/rss+xml" />
	<link>http://adscaptcha.com</link>
	<description></description>
	<lastBuildDate>Mon, 30 Aug 2010 19:42:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Gmail Registration and Captcha Cracking</title>
		<link>http://adscaptcha.com/2009/08/17/gmail-registration-and-captcha-cracking/</link>
		<comments>http://adscaptcha.com/2009/08/17/gmail-registration-and-captcha-cracking/#comments</comments>
		<pubDate>Mon, 17 Aug 2009 19:31:21 +0000</pubDate>
		<dc:creator>Ads Captcha</dc:creator>
				<category><![CDATA[Interesting Captcha]]></category>
		<category><![CDATA[bot spammers]]></category>
		<category><![CDATA[captcha cracking]]></category>
		<category><![CDATA[captcha spam]]></category>
		<category><![CDATA[cracking gmail registration]]></category>
		<category><![CDATA[gmail cracked]]></category>

		<guid isPermaLink="false">http://adscaptcha.com/?p=48</guid>
		<description><![CDATA[Is the Captcha test not perfect? It sure looks like it can be improved, as not too long ago some bot spammers had succeed to crack the Captcha codes of the registration process to Gmail…
]]></description>
			<content:encoded><![CDATA[<p>Not too long ago the Gmail registration, which supposed to be secured by the highly popular captcha test, was <a href="http://securitylabs.websense.com/content/Blogs/2919.aspx">cracked by spammers</a>. What are the implications of this event? </p>
<p>First, let’s start with clarifying the meaning of that strange word &#8220;CAPTCHA&#8221;.<br />
Captcha is an abbreviation of &#8220;Completely Automated Public Turning test to tell Computers and Humans Apart&#8221;.</p>
<p>The captcha test is used all over the online world by all kinds of websites who want to verify the user who&#8217;s signing up to them is a human and not a robot or some automated machine.<br />
In other words, by using the Captcha test all spammers are supposed to be filtered out.</p>
<p>Unfortunately, it has been discovered lately that spammers have succeeded to create bots that are capable to open Gmail accounts and thus can attack and abuse the infrastructure of Google mail.</p>
<p>Gmail, as you may know, is a free service by Google. It is considered as a highly user-friendly, simple and flexible platform that enables over 6000 MB of storage for free (plus more 10GB for a symbolic fee of 20$ a year) and it has tens of millions of satisfied users from all over the world.</p>
<p>The bots succeed to open accounts by feeding all the data required on the sign up page and then cracking the Captcha (usually displayed at the bottom, at the end of the registration process). Bots are trying to create new accounts as many as possible, by using 2 hosts in the process of cracking the Captcha code. Once the first host fails to break the code the second host gets into action.<br />
The cracked Captcha codes are stored in a domain located at United States.</p>
<p>Luckily, Captcha is not an easy test for machine computers or bots and in spite of endless repeated cracking attempts <strong>only 20% Captchas are busted</strong>. </p>
<p>Is it possible to overcome the Captcha cracking problem on Gmail registration process?<br />
I guess only time will tell…</p>
]]></content:encoded>
			<wfw:commentRss>http://adscaptcha.com/2009/08/17/gmail-registration-and-captcha-cracking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
