Google already has a solution for this, why are they ignoring it? Google allready supports 2FA with the new U2F protocol. With this protocol the app id (uri) i

Google already has a solution for this, why are they ignoring it? Google allready supports 2FA with the new U2F protocol. With this protocol the app id (uri) is part of the process and its provided by the browser. Thus phishing attacks will fail. Sadly Firefox and other broswers do not yet support this, only Chrome. I really hope this replaces the old 2FA TOTP style and specially SMS. For people who want to use both, there is a nice solution. You can use YubiKey as your U2F token and for websites that don't support this you can use the YubiKey as your 2FA with the help of a android app called 'Yubico Authenticater' and NFC. I prefer it to Google Authenticator because I can move between android devices (just came in useful when my phone broke). Google does not yet support NFC U2F on their mobile browsers as far as I know. Thats very sad, I really want to be able to disable HOTP solution. See the protocol here: https://image.slidesharecdn.com/fidou2fin10minutescis2015-150622164512-lva1-app6891/95/fido-u2-f-in-10-minutes-cis-2015-17-638.jpg?cb=1434991550 https://image.slidesharecdn.com/fidou2fin10minutescis2015-15...