6 ms·
After using TOTP like Google Authenticator since around 2013, I now think the friction needed is just too great. Especially for banks which log you out after 15
by kccqzy 7y ago
After using TOTP like Google Authenticator since around 2013, I now think the friction needed is just too great. Especially for banks which log you out after 15 minutes or so of idleness. Google doesn't do that.
Not to mention Google Authenticator deliberately prevents these stored tokens to be backed up and transferred to a different device, which makes upgrading devices troublesome.
I wish everyone would start using Yubikeys. WebAuthn is now widely supported by browsers.
- jkepler 7y agoWhy not use an open TOTP app like AndOTP. I use it all the time for sites that claim to require Google Authenticator, it works, and its easy to backup the secrets as plain text or encrypted with a password. I keep it current on my primary phone and a cheap offline backup, in addition to backing up the encrypted secrets file.
- balladeer 7y agoI use Authy on iPhone and Mac. I am looking for an OSS replacement but would not want to setup everything from scratch after I change device reinstall the app like Google Authenticator.
- sneak 7y agoBitwarden does a decent job of storing and syncing TOTP codes. Make sure you always use a long password with Bitwarden though, to avoid a known and unpatched issue with their password-based key derivation.
- balladeer 7y agoOh, didn’t know BitWarden did it. That’s my password manager :)
- AaronFriel 7y agoWhat issue is that?
- sneak 7y agoCVE-2019-19766 https://github.com/bitwarden/server/issues/589 https://github.com/bitwarden/server/issues/589
- __david__ 7y agohttps://freeotp.github.io/ https://freeotp.github.io/ iPhone backups back up its data correctly—my codes survive new phone restores where they do not with Google Authenticator.
- samatman 7y agoThanks for sharing this link. I've wanted to get off Google Authenticator for awhile now, mostly because of the backup-restore problem, also a general trend of limiting my involvement with the company.
- Terretta 7y agoDon’t put them in google authenticator. https://support.1password.com/one-time-passwords/ https://support.1password.com/one-time-passwords/
- obituary_latte 7y agoWow that’s awesome! I had no idea 1Password had this functionality so thanks for sharing. I just had a rough time after upgrading my phone dealing with Google Authenticator since I hadn’t realized my Auth info would not migrate along with the rest of my data...
- jdeibele 7y agoThat sounds good but put them in Authy. That lets you have multiple devices whereas Google limits you to one device. It's great that people use can use one app for both factors but it seems less secure than two apps. For example, use Authy for TOTP and LastPass for long passwords. That's two things that have to be compromised. And both of them allow you to have multiple devices (for example iPhone and iPad).
- kccqzy 7y agoYes that's what I've been doing after being burned by Google Authenticator once. Not to mention I actually prefer the UI design of 1Password.
- jorvi 7y agoIts great functionality but it reduces your security. Say someone somehow figures out your 1Password password and security key - if you store your OTPs in Authy, your passwords are useless (well, less useful anyway). If you store your OTPs in 1Password, they have the keys to the kingdom.
- SpaethCo 7y agoThis is technically true, but the most likely scenarios that result in the discovery of your secret key (128bits of entropy) + master password (?? additional bits) involve things like a device compromise. If your machine is compromised, you’re probably already exposed to things like session cookie stealing. At that point your attack surface is already blown wide open. The biggest thing 2FA protects against is credential stuffing. If you’re using a password manager and have high entropy site-unique passwords, the additional entropy by TOTP is mostly moot anyway.
- lutorm 7y agoIsn't that solvable by not requiring 2fa for "registered" devices?
- rorykoehler 7y agoUse Authy instead of Google Authenticator. Problem solved. RFC 4226 doesn't specify that you can't have shared devices.
- LordAtlas 7y agoUse Authy. Can be transferred to a new device.
- thaumasiotes 7y ago> Not to mention Google Authenticator deliberately prevents these stored tokens to be backed up and transferred to a different device, which makes upgrading devices troublesome. It doesn't offer export in the app UI. It's not doing anything to prevent you from backing up the tokens yourself; they're stored in the clear in the sqlite database for the app. If that's too much for you, there's a good chance https://github.com/puddly/android-otp-extractor https://github.com/puddly/android-otp-extractor can get them automatically.
- riffraff 7y agoAFAIK, in the EU all banks are required to have "strong authentication" which usually means using 2FA via biometric authentication on your phone. Classic Google Authenticator does not seem much more friction than that.
- justincormack 7y agoThat is not true. Banks in the EU seem to vary a lot, as the definition of “strong” is not defined (plus many banks have not introduced it yet). Biometric is definitely not required. I use hw tokens but at least one of my banks is trying to move to weaker auth.
- riffraff 7y agoI didn't say biometric is required, I said it's normal to have 2fa with friction, an hardware token is just as much friction as TOTP or biometric. I am surprised your bank is moving to a weaker auth, what does that mean? I have 3 bank accounts in 2 countries and they all switched to biometric because it's just a simpler experience then the hardware token or "mobile token" they used before.
- aloer 7y agoPeople recommend Authy. As far as I can tell they rely on cloud sync/backup like any other app in that space. Isn’t google authenticator not using this on purpose? Central account and sync is googles thing and yet they deem it too insecure. Completely understandable So how can using a central service that adds yet another attack vector be of value? What I would love to have is a paper export. Every time you add a new account to google authenticator you can print it as QR code for later reimport. Yes many services already provide this for you via recovery codes but having it on a per service basis directly from authenticator is probably much easier to use and not less secure Any reason this wouldn’t work?
- saagarjha 7y agoI can't see any, based on my slightly more than superficial dive into this area when working on my own two-factor application.
- brightball 7y agoWebAuthn is definitely the way to go. The security key approach is such a better user experience that the app based approaches.
- imtringued 7y ago>Not to mention Google Authenticator deliberately prevents these stored tokens to be backed up and transferred to a different device, which makes upgrading devices troublesome. If that were possible then you would face the same problems that reused SMS numbers suffer from.