Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit Guesses #21

Closed
GoogleCodeExporter opened this issue May 5, 2016 · 3 comments
Closed

Limit Guesses #21

GoogleCodeExporter opened this issue May 5, 2016 · 3 comments

Comments

@GoogleCodeExporter
Copy link

According to your example (http://code.google.com/p/kaptcha/wiki/HowToUse)
it seems that multiple guesses can be made on a single CAPTCHA image.

It could be beneficial to assign a new totally random code to the
KAPTCHA_SESSION_KEY on failure, forcing the "user" (bot?) to now guess a
completely random string with no help, or consider at a new image.

This is likely out of the scope of the project, but also recording the time
when the CAPTCHA image was made and enforcing a maximum time to solve it
could be good.

Original issue reported on code.google.com by jmferl...@gmail.com on 9 Aug 2008 at 4:53

@GoogleCodeExporter
Copy link
Author

For the first item, this would be implemented in your code. All Kaptcha does is 
serve an image and put a token 
in the session. If you want to reset it to a different value on failure, then 
go ahead. The only benefit for that is 
that you would be able to stop someone trying to brute force attack the kaptcha 
with a bot (ie: trying the same 
kaptcha value multiple times until they get it right. In my application, I do 
something like this instead: http://lookfirst.com/2008/06/red-listing.html

With regards to recording a time, I can add another parameter to the session 
that is a timestamp.

Original comment by latch...@gmail.com on 9 Aug 2008 at 5:55

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Ok, just added a Date to the session for you.

Original comment by latch...@gmail.com on 9 Aug 2008 at 6:14

  • Changed state: Fixed
  • Added labels: Milestore-2.3.1

@GoogleCodeExporter
Copy link
Author

Original comment by latch...@gmail.com on 9 Aug 2008 at 6:16

  • Added labels: Milestone-2.3.1
  • Removed labels: Milestore-2.3.1

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant