<story><title>The Inside Story of How Facebook Responded to Tunisian Hacks</title><url>http://www.theatlantic.com/technology/archive/2011/01/the-inside-story-of-how-facebook-responded-to-tunisian-hacks/70044/</url></story><parent_chain></parent_chain><comment><author>dansingerman</author><text>I have a bit of a problem with the description of the hack as &quot;The software was basically a country-level keystroke logger&quot;&lt;p&gt;I think this is unnecessary dumbing down.&lt;p&gt;For most readers who already knows what a keylogger is, it should be fairly obvious to them that this is not what they were doing.&lt;p&gt;For any reader who does not know what a keylogger is, describing the hack as being like a keylogger is not going to help them understand.&lt;p&gt;Furthermore, if you are in the demographic that know what a keylogger is, but can&apos;t see how that it is obvious that is not what was going on here, it just obscures what was really at play here: authenticating over (unencrypted) HTTP.&lt;p&gt;The writer probably did not want to make this a story about authenticating over HTTP, but misdescribing a central feature of the story is misleading.</text></comment>
<story><title>The Inside Story of How Facebook Responded to Tunisian Hacks</title><url>http://www.theatlantic.com/technology/archive/2011/01/the-inside-story-of-how-facebook-responded-to-tunisian-hacks/70044/</url></story><parent_chain></parent_chain><comment><author>Matt_Cutts</author><text>Good for Facebook. From the article, it sounds like they did two major things: 1) shift all Tunisian IP addresses to https instead of http. 2) anyone who logged out/in while the keylogger code was running was shown a social CAPTCHA. The CAPTCHA asks you to identify friends in photos.</text></comment>