<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Michael Jay Lissner</title><link href="https://michaeljaylissner.com/" rel="alternate"></link><link href="https://michaeljaylissner.com/feeds/tag/recaptcha" rel="self"></link><id>https://michaeljaylissner.com/</id><updated>2009-12-12T12:07:58-08:00</updated><entry><title>More Security Papers: Breaking ReCAPTCHA and Proactive Methods for Secure Design</title><link href="https://michaeljaylissner.com/posts/2009/12/12/more-security-papers-breaking-recaptcha-and-proactive-methods-for-secure-design/" rel="alternate"></link><updated>2009-12-12T12:07:58-08:00</updated><author><name>Mike Lissner</name></author><id>tag:michaeljaylissner.com,2009-12-12:posts/2009/12/12/more-security-papers-breaking-recaptcha-and-proactive-methods-for-secure-design/</id><summary type="html">&lt;p&gt;Two more security papers&amp;nbsp;today. &lt;/p&gt;
&lt;p&gt;In the first, &lt;a href="https://michaeljaylissner.com/pdfs/breaking-recaptcha.pdf"&gt;&lt;strong&gt;Breaking ReCAPTCHA&lt;/strong&gt;&lt;/a&gt; I discuss a few methods that 
ReCAPTCHAs can be hacked, and talk a bit about the ways that they were 
attacked by the Anonymous hacker group. I should mention at the outset that
none of the approaches here are particularly useful though, 
and that ultimately, the hacker group beat ReCAPTCHA by simply out 
numbering&amp;nbsp;it.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://michaeljaylissner.com/pdfs/proactive-security.pdf"&gt;The &lt;em&gt;second paper&lt;/em&gt;&lt;/a&gt; is a brief discussion of some approaches an 
organization might take when beginning a project in which security is a 
high concern. Essentially, it takes a chronological approach, 
from the start to the end of the&amp;nbsp;project. &lt;/p&gt;
&lt;p&gt;Enjoy.&lt;/p&gt;</summary><category term="security"></category><category term="captcha"></category><category term="ReCAPTCHA"></category><category term="Design"></category></entry></feed>