News for hackers. Stuff that matters.
Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail... by sauteedbiscuits on Saturday June 02, 2012 @08:40AM (#4057940)
The biggest weakness's to 2 factor auth are:

1: You can remove 2 factor auth without having to enter the auth code. So if your computer gets a virus, someone can just remove 2 factor auth via your browser

2: The "app specific passwords" are full on backdoors. If one of your app specific passwords gets hijacked, someone can login to your gmail with it and then remove the 2 factor auth pass (See above)

* http://productforums.google.com/forum/#!category-topic/mobil...

Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail... by reedlaw on Saturday June 02, 2012 @09:31AM (#4058017)
Aren't app specific passwords simply single-factor auth tokens, thus defeating the purpose of using two factor auth? Wouldn't a sufficiently complex pass-phrase be just as secure?
Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail... by aristidb on Saturday June 02, 2012 @10:01AM (#4058069)
No, because each app has a different token and you can revoke them individually.

Google does want people to use OAuth instead of app-specific passwords as much as possible, but sometimes that's not possible or just isn't done. Then you at least get some security from not posting the same password to a million places.

Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail... by yock on Saturday June 02, 2012 @11:14AM (#4058230)
Google's own products don't even conform to this. My Galaxy Nexus and Chrome browser requires app-specific passwords.
Re:Cloudflare Attack Post Mortem; Apparent Google Apps/Gmail... by kolev on Saturday June 02, 2012 @06:30PM (#4059397)
The latest version of Chrome dev (21.0.1155.2 dev-m) does not require an app-specific password - it works with the OTP if you have it enabled, but at least for me the sync is broken at this point.