Created
December 8, 2016 18:56
-
-
Save mollybrown/33b983dccd52150cf8c50fb8f55471dc to your computer and use it in GitHub Desktop.
CAPTCHA lightning talk outline
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Intro | |
What is CAPTCHA? (its an acronym!) | |
What is the purpose/motivation? | |
- Present a problem/test that is very difficult for computers to solve but not for humans as a security measure. | |
- Generally used whenever you want to prevent a bot from automatically completing a process (account registration, protecting comment spam in blogs, preventing automatic downloading of content, etc.) | |
2. Overview of different iterations/versions | |
CAPTCHA: first uses began in 2003 | |
- warped text | |
reCAPTCHA: 2007 | |
- Same purpose as CAPTCHA, also assists in the digitization of books by presenting images of words flagged as hard to read for optical character recognition (OCR) software. | |
- Google maps house number photos added in 2012 | |
- Image selection added in 2014 | |
no CAPTCHA reCAPTCHA: 2013 | |
- no text or images, just a checkbox. | |
- relies on behavioral analysis of browser's interactions with the CAPTCHA. | |
invisible reCAPTCA: December 2016! all new! who knows! | |
3. How they can be broken | |
CAPTCHA Weaknesses: CAPTCHA farms, exploiting design flaws, machine learing. | |
text reCAPTCHA Weaknesses: Same issues as original CAPTCHA implementation. | |
image reCAPTCHA Weaknesses: Image annotation | |
noCAPTCHA reCAPTHA Weaknesses: By manipulating browser history, a bot can pick up enough cookies to appear to have "human" behavior. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment