Re:Google Rolls Out Two-Factor Authentication For Everyone.
by groby_b on Thursday February 10, 2011 @05:04PM
(#2204020)
Which means you phished it once. Which means you need to take drastic actions to exploit it, a slow buildup over time is not an option.
Which in turn means you're more likely to get detected. It's not full protection - you'd still need a second channel for that - but it's better than nothing.
Re:Google Rolls Out Two-Factor Authentication For Everyone.
by roc on Friday February 11, 2011 @09:59AM
(#2206500)
It is certainly better than nothing. I just took issue with the article's repeated insistence that it'd make phishing harder/impossible.
It does many good things. That is not one of them.
Re:Google Rolls Out Two-Factor Authentication For Everyone.
by lutorm on Thursday February 10, 2011 @05:11PM
(#2204039)
For the systems I log in to, each SecurID code is only valid once. If you want to log in again, you need to wait until a new code is available and use it.
Re:Google Rolls Out Two-Factor Authentication For Everyone.
by teejae on Friday February 11, 2011 @04:58AM
(#2205775)
See:
http://en.wikipedia.org/wiki/HOTP
and
http://en.wikipedia.org/wiki/Time-based_One-time_Password_Al...
You can download the Google Authenticator app.
These algorithms are known. You can implement it yourself if you wanted to.
Unless I'm missing something, RFC 4226 sounds like the RSA SecurID system I've worked with before; which is essentially equivalent to Blizzard's system for World of Warcraft.
In which case, my criticism stands. It's trivially more difficult to phish a keycode and the limited window of opportunity is simply a non-issue.[1]
Unless Google is calculating a one-time pad based on the individual login attempt and sending it along a second channel to the registered user, there'll be almost no reduction in phishing.
[1] The tens of seconds a keycode is valid are more than enough to establish a connection.