Security Blog

The latest news and insights from Google on security and safety on the Internet

reCAPTCHA just got easier (but only if you’re human)

25 ottobre 2013
Share on Twitter Share on Facebook
Google

33 commenti :

Unknown ha detto...

Need to improve. some bot still can read it. maybe better if we can have some variation in number position. color and other custom things. so bot can not detect all. maybe they can detect the default, but with custom setting it will make more difficult

25 ottobre 2013 alle ore 20:32
Jono ha detto...

Interesting, but if the system has already determined that someone is human then why even present the easy captcha?

26 ottobre 2013 alle ore 06:38
mjpg ha detto...

The above is a little confusing:

"serve ... legitimate users CAPTCHAs that [are] easy to solve. Bots ... will see CAPTCHAs that are ... difficult ...

you’ll encounter CAPTCHAs that are a breeze ... Bots ... won’t ... see them."

If you can determine in advance who is a bot and who a human, why do you need a CAPTCHA at all?

26 ottobre 2013 alle ore 11:04
Unknown ha detto...

What's the point of a captcha? To determine if you're a human.

So... if you already know that I'm a human, why show the captcha in the first place?
Unless the recaptcha system is really in place to just decipher the streetview photos of house numbers

btw, to leave this comment, I didn't get a numerical captcha. Am I a machine?

26 ottobre 2013 alle ore 17:13
Greg Afinogenov ha detto...

What about the text digitization function that made reCAPTCHA so valuable in the first place?

27 ottobre 2013 alle ore 20:05
timeofmind ha detto...

If the software is capable of differentiating between bots and humans before presenting the captcha, then what is the point of the captcha?

28 ottobre 2013 alle ore 17:14
Dan F. ha detto...

Do I need to make any changes on my web site that uses reCAPTCHA in order to take advantage of these improvements, or are the changes automatic?

29 ottobre 2013 alle ore 12:26
Tommy marsboer ha detto...

How can I get in contact with the team behind SafeBrowsing?

I have a massive list of domains I think SafeBrowsing should include.

29 ottobre 2013 alle ore 15:15
Singularity Utopia ha detto...

I am human but things have not become easier for me :-(

Where do I complain?

http://imgur.com/InqcLyx

30 ottobre 2013 alle ore 17:41
Lucas Bustamante ha detto...

How do I enable numeric only recaptcha? It's still showing as letters to me.

2 novembre 2013 alle ore 18:35
spur011 ha detto...

This particular user, however, is happy to continue to help decipher scanned texts via reCAPTCHA, even if the computer thinks I'm human.

4 novembre 2013 alle ore 05:12
Anonimo ha detto...

And obviously, the non-generated numbers are house/mailbox numbers from the Streetview database that Google wants to make semantic.

[EDIT: Solving a ReCAPTCHA to comment on an article about ReCAPTCHAs seems a bit too much of a good thing. :P
1642 utofio. Wavy words are not quite done with, it seems.]

5 novembre 2013 alle ore 13:26
Unknown ha detto...

The megatypers Captcha works awesome and pays well so do register and use the invitation code which is mandatory to register.
Invitation CodeS : 7VF1
7VF2

13 novembre 2013 alle ore 11:22
Parvez Khan ha detto...

Hi
How can i make it only numeric
we have used it in one site but the alphabets captacha is most of the time unreadable for many users
can you tell the settings how to make it only numeric for making our life easy

Thanks and regards
Parvez

24 novembre 2013 alle ore 09:49
Mohamed Ramadan ha detto...

How can I configure the reCaptcha control to use this update? I found the current version is still showing very difficult words to read.

22 dicembre 2013 alle ore 17:15
Freedom Fighter ha detto...

Actually, the captchas are only easier if you have any cookies from Google.
So its actually Google's way of punishing those that don't use their services.

Open up a private browser window and try a captcha, you'll know that they're significantly harder, not even difficult, they just automatically fail.

13 gennaio 2014 alle ore 14:19
Freedom Fighter ha detto...

Actually, the captchas are only easier if you have any cookies from Google. Open up a private browser window, you'll notice that the captchas have black blobs in them and automatically fail.

If you're being tracked by Google's cookies, then the captchas are easier. If you're not being tracked, then its harder.

13 gennaio 2014 alle ore 14:21
Bruce A. Pokras ha detto...

The example shown shows up on my home Mac using Safari. However, on my Windows PC using Internet Explorer at work I am now seeing words that are even more indecipherable than in the past (two words with a black ink blot over them). This is at the "Public PAIR" page of the USPTO.

15 gennaio 2014 alle ore 15:35
Website Design and Support ha detto...

so how do we get the new AP?
Woooow you are not even using it for this form, will this might be the answer to my q.

28 gennaio 2014 alle ore 19:58
PhistucK ha detto...

I personally think this is too bad. The point of reCAPTCHA, beside detecting bots, is to improve OCR. Improving OCR for numbers is not that helpful (if that is what it is even doing, but I assume it does not) as improving OCR for letters and other characters.
It was a very nice and helpful idea and this essentially ruins it. :(

30 marzo 2014 alle ore 16:03
Unknown ha detto...

OCR has become very advanced, to the point that it reads the distorted letters with better accuracy than some humans.

I'm pretty sure there's still a benefit (Google Street View) from getting the numbers right. As well as preventing bots abusing the system.

So, no, it is not ruined.

16 aprile 2014 alle ore 19:45
How to get rid of blogger onboarding ha detto...

I am confused - the text implies that form of captcha (numbers vs. twisted letters) depends on whether or not the system believes I am a human. But if the system already knows if I am a human, BEFORE I am presented a captcha, what is the point of showing it.
Do I understand the term CAPTCHA ("Completely Automated Public Turing test to tell Computers and Humans Apart") in a wrong way?

18 aprile 2014 alle ore 13:19
Andi ha detto...

To me it looks like the (second) numbers are house numbers. So perhaps it will help improve Google Maps?

23 maggio 2014 alle ore 04:25
mosaic design education ha detto...

How to use this new captcha? Like the one being asked in this comment box ?

24 maggio 2014 alle ore 13:02
Unknown ha detto...

Hi,

my website always serves the very hard recaptchas. But I'm human!

Why am I always detected as a bot?

Best regards,
--Martin

30 maggio 2014 alle ore 03:16
Unknown ha detto...

I run a website for older people, and need to more closely hug the line in allowing bots through versus the clients. Through testing, it seems that if the system ever triggered to think the client is a bot then they would essentially become locked out of the system as the words would be too difficult for them.

8 giugno 2014 alle ore 08:01
Mir ha detto...

reCAPTCHA is not showing good please check this page http://www.topseoforum.com/ucp.php?mode=register

1 luglio 2014 alle ore 07:06
CodeSwimmer ha detto...
Questo commento è stato eliminato dall'autore.
10 luglio 2014 alle ore 13:51
CodeSwimmer ha detto...
Questo commento è stato eliminato dall'autore.
10 luglio 2014 alle ore 13:52
Unknown ha detto...

If I'm understanding this correctly, in an attempt to block spam and bots, the captcha will also get increasingly difficult over multiple attempts while being testing by web designers tweaking their code eventually bringing testing to a halt!

15 luglio 2014 alle ore 14:01
Nicholas ha detto...

Alan, Check out http://techcrunch.com/2012/03/29/google-now-using-recaptcha-to-decode-street-view-addresses/


At first reCaptcha was used to help digitize the 30% of words current OCR tech couldn't solve.

Now that google owns recaptcha they are using it to help decipher google street maps house numbers, street signs and business names.

I don't think it's ruined.

16 luglio 2014 alle ore 18:31
Daniel Saner ha detto...

Once reCAPTCHA (wrongly) determines you're a bot, you start being served challenges with two almost impossible to decipher random letter sequences (both of them "control words").

http://i.imgur.com/01F2eES.png

Maybe you think you can read this, but believe me, you can't. I tried "ryntrInt llyHFrv" on this particular one, and it was wrong. And they're all this bad. It takes me an average 10-15 tries to get one of them right, which of course means that I'll never get out of the "hole" of reCAPTCHA thinking that I'm a bot, because I fail so often.

I appreciated getting the easier, Street View captchas while I could still get them. But this adaptivity approach fails badly when going into the other direction (making challenges harder than classical reCAPTCHAs, rather than easier).

From my very limited dataset of just my own encounters, reCAPTCHAs human/bot pre-distinction is atrociously bad. And from my own horrible experiences with it, assuming that many of my own legitimate users will have to deal with the same, I've had no choice but to ditch reCAPTCHA entirely. I cannot afford to subject my users to this torture and scare them away forever. It's gone too far. Especially since I hear that there are bots out there with automatic captcha solvers that have a much better hit rate than myself at this point.

2 agosto 2014 alle ore 22:20
Mike ha detto...

Any way to fix the issue whereby the big reCAPTCHA default logo is displayed, which makes users click on it because it includes a huge circle with arrows that makes people think that is the place to click on to reload a new set?

That logo has always been a big problem in terms of usability because it makes people click on it, rather than on the nearby very similar (but much smaller) reload symbol. I am surprised the issue is still there, as illustrated on top of this post.

3 agosto 2014 alle ore 23:52

Posta un commento

  

Etichette


  • #sharethemicincyber
  • #supplychain #security #opensource
  • android
  • android security
  • android tr
  • app security
  • big data
  • biometrics
  • blackhat
  • C++
  • chrome
  • chrome enterprise
  • chrome security
  • connected devices
  • CTF
  • diversity
  • encryption
  • federated learning
  • fuzzing
  • Gboard
  • google play
  • google play protect
  • hacking
  • interoperability
  • iot security
  • kubernetes
  • linux kernel
  • memory safety
  • Open Source
  • pha family highlights
  • pixel
  • privacy
  • private compute core
  • Rowhammer
  • rust
  • Security
  • security rewards program
  • sigstore
  • spyware
  • supply chain
  • targeted spyware
  • tensor
  • Titan M2
  • VDP
  • vulnerabilities
  • workshop


Archive


  •     2025
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2024
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2023
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2022
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2021
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2020
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2019
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2018
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2017
    • dic
    • nov
    • ott
    • set
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2016
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2015
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2014
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • apr
    • mar
    • feb
    • gen
  •     2013
    • dic
    • nov
    • ott
    • ago
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2012
    • dic
    • set
    • ago
    • giu
    • mag
    • apr
    • mar
    • feb
    • gen
  •     2011
    • dic
    • nov
    • ott
    • set
    • ago
    • lug
    • giu
    • mag
    • apr
    • mar
    • feb
  •     2010
    • nov
    • ott
    • set
    • ago
    • lug
    • mag
    • apr
    • mar
  •     2009
    • nov
    • ott
    • ago
    • lug
    • giu
    • mar
  •     2008
    • dic
    • nov
    • ott
    • ago
    • lug
    • mag
    • feb
  •     2007
    • nov
    • ott
    • set
    • lug
    • giu
    • mag

Feed

Follow
Give us feedback in our Product Forums.
  • Google
  • Privacy
  • Terms