Ha, fair - and my desktop too, since I currently use the Authy desktop app. However, that’s two different sets of credentials an attacker needs to steal/bypass, and two chances to stop them in time.
You can have 2 different keys DB on keepassXC with different passwords, you can even try to save them in separate remote locations. The key points are data interoperability over different devices and its portability over different services, because the worst thing that can happen is that your favourite app, from where you cannot use or move your credentials elsewhere (like the Steam Guard app for instance), one day might stop working suddenly leaving you unable to access your accounts.
If you use Linux then OTPClient works great with Aegis since it can open Aegis export files directly. I’ve set up Aegis to make an export whenever I change something, I sync the exports automatically to my PC, and I open them with OTPClient there.
OTPClient can ask for the export password each time you open it and will close itself automatically if it’s not used for a while.
You can also use it to export the 2FA codes further in various formats, show the QR code for any of them, and all kinds of useful features like that.
Spent an hour last night moving to 2FAS. Authy doesn’t make it easy – unlike their competitors, they don’t offer an export feature.
It launched an NFT based donation program: https://2fas.com/donate/
and it is not available on F-Droid.
I’d go with Aegis for an App on Android, or a Bitwarden/KeepassXC password manager which can both handle 2fa tokens too.
I don’t like the thought of having my passwords and 2FA live in the same place - that seems to miss the point a bit.
Like your phone?
Ha, fair - and my desktop too, since I currently use the Authy desktop app. However, that’s two different sets of credentials an attacker needs to steal/bypass, and two chances to stop them in time.
You can have 2 different keys DB on keepassXC with different passwords, you can even try to save them in separate remote locations. The key points are data interoperability over different devices and its portability over different services, because the worst thing that can happen is that your favourite app, from where you cannot use or move your credentials elsewhere (like the Steam Guard app for instance), one day might stop working suddenly leaving you unable to access your accounts.
If you use Linux then OTPClient works great with Aegis since it can open Aegis export files directly. I’ve set up Aegis to make an export whenever I change something, I sync the exports automatically to my PC, and I open them with OTPClient there.
OTPClient can ask for the export password each time you open it and will close itself automatically if it’s not used for a while.
You can also use it to export the 2FA codes further in various formats, show the QR code for any of them, and all kinds of useful features like that.
Aegis is great.
deleted
yeah but F-Droid also insures the authenticity and reproducibility of the binary builds
First thing I check before I commit to something: export feature.
Yeah, this is going to be a pain in the ass. At least I have until summer.
But you found a way. How?
Literally went to every site in Authy and removed 2FA and then re-added it with the new app.