andOTP VS google-authenticator

I love F-Droid and try to use apps from there whenever possible.

I did recently discover that andOTP is no longer maintained, though. I've switched to Aegis since.

https://github.com/andOTP/andOTP

I use andOTP[0] which auto-exports an encrypted backup to a local folder, which is then synced with Syncthing[1] to my NAS.

It's seamless and doesn't need an internet connection.

- [0]: https://github.com/andOTP/andOTP

- [1]: https://syncthing.net/

- AndOTP github project is archived in june 2022: https://github.com/andOTP/andOTP

I used FreeOTP before that, which is also fine. I switched because maintenance had been fairly uncommon and there were some minor issues bugging me, but it seems to have picked up again recently, and it's backed by Red Hat as an entity for better or for worse. andOTP is officially deprecated, so I recommend switching to either of those.

At the moment this works with encrypted backup files from andotp and aegis and it totally fullfills my lazyness needs. :)

I was happily using andOTP but seems like it has been unmaintained since June - https://github.com/andOTP/andOTP.

I wish F-Droid or Play Store had a feature like GitHub's 'Archived' to inform users.

You can use whatever 2FA you want, but you need to extract the secret key for it using some scripts. i did it a while ago and i have both blizzards and steams 2fa on Aegis on android, also works in KeepassXC. I think the 2fa app needs to have support for it but it works. https://github.com/andOTP/andOTP/wiki/Shared-secrets

I would switch to andOTP since it allows you to export the keys.

otpauth:// is a de-factor standard, since Google Authenticator uses it: https://github.com/google/google-authenticator/wiki/Key-Uri-...

Random question if you're using TOTP why not just give the user the secret when signing up as a Google Authenticator URI encoded in a QR code? Then you won't need to futz around with sending it to them afterwards. You can even use a library like qrcode.js so you don't generate the barcode server side either.

Locker can generate Time Based OTP codes parsing TOTP urls stored under a special key named totp.

(Examples> https://github.com/google/google-authenticator/wiki/Key-Uri-Format)

If we're talking about the encrypted Authy TOTP secrets and IF they get cracked or guessed, Authy does store the email in the name of the item. Having the name, service and the secret within the QR code's URI is normal and the standard for TOTP. The only thing the hackers won't have is the password.