Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Because its already stretching 2FA quite a bit to have it as just another program running on what is essentially a general purpose computer.


I can't quite see the difference between copying numbers out of an app, and sending a secure string to a server with HTTPS. If anything, doing it in the back end would allow for even longer strings. A signed message or a challenge-response with a large secure asymmetric key.


partly because this is a bit easier to implement, so the barrier to entry is lower.

Also, no network access is required for OATH TOTP tokens to work (they are derived from a shared secret and number of 30s segments of time since Unix epoch) if you are somewhere with no mobile coverage, or are abroad and don't want to pay roaming charges. You can also get hardware tokens for this reason.

Finally, there is no guarantee the network between your mobile device and the web app are secure, and as we've seen with some nation states abusing wildcard SSL certificates, even SSL isn't necessarily a defense.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: