For Android, Aegis. You can get it it on Play, on one of the numerous *-Droid sources or straight from GitHub with Obtanium.
Simple to use, open source, does encrypted exports which I regularly backup (along with Bitwarden and SimpleNotes exports) to one of these (Amazon link). It's perfect for me.
Moved to Raivo earlier this year and it’s great. Unfortunately it was just sold to a private company, so I’m looking for alternatives. From the replies here, might try 2FAs
I recommend KeePass and I encourage everyone to consider it given its platform-agnostic portable format. What happened to Raivo cannot happen to KeePass and its more of a universal solution as opposed to 1) Android: Aegis 2) iOS: Tofu or OTP etc.
All of those are very good apps but the problem remains that they all have their own peculiar/specific format that doesn't necessarily play nice with any other app. KeePass is a convention/format that doesn't really vary between implementations.
Edit: It also allows for choice in whether to keep it local or to safey sync in your choice of cloud service without exposing the contents unencrypted. If you don't want to manage any of that, I would recommend Bitwarden and paying the $10 once and see if you're still fine the next year without having to resubscribe if thats a problem for you.
The problem here would be storing your passwords along with your 2fa. You're basically giving away every information needed to enter your accounts in case someone get access to your vault.
The best option would probably be using both KeePass and BitWarden. You store your passwords in one and your 2fa in the other.
IOS is much harder. Right now, probably "2FAs". Authy is owned by Twilio, Raivo was just bought out by an advertising company, and the others are either too small to get the exposure required for any level of security or charge for the feature.
It's less that Twilio specifically owns it than problems resulting from corporate ownership. Briefly:
You can't get your data out of Authy. Actually you can, but it's a long annoying process involving installing an out of date chrome extension and using developer tools.
Privacy issues. Authy links a lot of data including location to your identity.
Authy supports SMS account recovery (which is inherently insecure) and doesn't allow users to disable it.
I've always been of the mindset that storing your 2fa next to your passwords at least partially defeats the purpose of 2fa.
The two types of attacks I worry about would be a hacked/leaked password from a third party site, or your password manager being compromised. While the latter is far less likely, it is still something I'd like to protect myself from as much as possible.
If my password manager is compromised, I'm well and truly fucked. If one site has shitty security (odds of which are approximately 1), having 2FA might help.
I hadn't even noticed. With all the mentions of Aegis it looks like I was behind the times. Aegis was able to import my andOTP entries so I'll give it a try.
For ios used to say raivo but i would honestly just make a kdbx file just for your totp seeds only and then use something like keepassium or strong box. I think those allow cloud syncing too but im not sure still keep local backups
Still use Google Authenticator. I know there are alternatives out there that have other features but I'm a pretty strong believer that my 2FA shouldn't be backed up digitally. I keep any recovery information offline and prefer it that way.
Las time I checked those that require a Microsoft or other propietary authenticator app that isn't Google's. They would force you to first use that propietary app and later export to Aegis. Correct me if I'm wrong, of course.