Earlier quoted context omitted.
Didn't it change the web page on your computer browser after you successfully added it into Google Authenticator? I suppose you could always take a photo of the QR code and then rescan that. Text seems simpler. edit: Anyone else remember this behavior? Old version? Browser specific?
It changes when you input current code. You can scan it multiple times, print it, and then input the code from one of your devices.
Adding a security key to Gmail
21–30 of 126 posts
Re: Adding a security key to Gmail
#22I'd like some advice about safely accessing gmail from your phone. In particular an android phone that might not have the latest version of android on it. Also for situations where not only do you access your gmail from your phone but also your google authenticator app is installed on it.
The recommended way are app passwords. You basically generate a password for each app that needs to access your mail account. You can easily revoke access for a single app in case something goes wrong. Also, nobody gets the chance to read your actual password.
I'm actually using Outlook as my e-mail client now. It's surprisingly snappy for my minimal needs. Maybe I should switch to iCloud for e-mail, and aim for the trifecta...
Re: Adding a security key to Gmail
#23Earlier quoted context omitted.
Only Chrome supports U2F. Firefox has experimental support of you enable special flags in about:config but I never got it to work. U2F will be superseded by Web Authentication [0] that includes U2F and will be supported by all major browsers. Edge includes draft spec API that uses TPM to store keys. [0]: https://w3c.github.io/webauthn/
You can use U2F in firefox with extension. Last time I tried it worked. However I use chrome most of the time so I am not sure if it still does. https://addons.mozilla.org/en-Us/firefox/addon/u2f-support-a...
Re: Adding a security key to Gmail
#24Re: Adding a security key to Gmail
#25Thanks for writing this! One nitpick: the guide says "If you're curious why it's important to not have a phone number on your account, see the security key FAQ", but the linked security FAQ doesn't actually appear to say why it's important.
Sorry about that, I'm updating that FAQ next. The answer is that SMS is not a secure second factor (it's easy to hijack and eavesdrop on), and in some cases when you give a service a phone number, it becomes possible to take over the account with just control of the phone number.
Re: Adding a security key to Gmail
#26The article mentions Yubikey at $18. As an alternative, the Nitrokey U2F is only €9 (€11 including delivery) https://shop.nitrokey.com/shop/product/nitrokey-u2f-5
Re: Adding a security key to Gmail
#27The article mentions Yubikey at $18. As an alternative, the Nitrokey U2F is only €9 (€11 including delivery) https://shop.nitrokey.com/shop/product/nitrokey-u2f-5
Plus, unlike with Yubikey, Nitrokey has open-sourced both hardware and firmware [1]. [1] https://github.com/nitrokey
Re: Adding a security key to Gmail
#28I'd like some advice about safely accessing gmail from your phone. In particular an android phone that might not have the latest version of android on it. Also for situations where not only do you access your gmail from your phone but also your google authenticator app is installed on it.
Re: Adding a security key to Gmail
#29Thanks for writing this! One nitpick: the guide says "If you're curious why it's important to not have a phone number on your account, see the security key FAQ", but the linked security FAQ doesn't actually appear to say why it's important.
Because it can be a way to compromise your account[0]. HN discussion[1]: [0]: https://blog.coinbase.com/on-phone-numbers-and-identity-423d... [1]: https://news.ycombinator.com/item?id=12597609
How in the world is a random guy supposed to do this sort of thing? Anyone have any tips for people who get into these situations and who aren't already BFFs with C-level executives of phone companies or something like that?
Re: Adding a security key to Gmail
#30Earlier quoted context omitted.
The recommended way are app passwords. You basically generate a password for each app that needs to access your mail account. You can easily revoke access for a single app in case something goes wrong. Also, nobody gets the chance to read your actual password.
Unfortunately, you can't access GMail over its "native" protocol using app-specific passwords: it'll only work for IMAP. And the GMail client is a terrible IMAP client. My inbox and folders / labels would constantly desync. I'd moved to FastMail a while back and the problem persisted, so I'm reasonably sure it's the client. I'm actually using Outlook as my e-mail client now. It's surprisingly snappy for my minimal ne…