>your phone gets stolen or stops working >can't log in to websites and emails that use 2FA
explain this retards. Why can't we have a KeePass-like database for 2FA which means that we could have the 2FA backed up to multiple devices incase our phone dies permanently
Up to you. The same totp code can be copied and pasted in both applications.
Luke Long
Is KeepassXC better than the normal one?
Michael Kelly
>explain this retards Everything that supports 2FA will give you another way to log in if you lose your phone. Most give you a list of backup codes, which you should print out and store in a safe place. If you lose your phone, you can log in with a backup code to disable 2FA. Some don't have backup codes, but have other dubious backup methods, such as fallback to SMS 2FA (which is shit and insecure.)
Source: I broke my phone like an idiot, but I didn't lose access to any of my accounts.
>Why can't we have a KeePass-like database for 2FA You can. KeePassXC supports TOTP, but it almost completely defeats the purpose of 2FA to store the TOTP codes in the same database as your passwords.
Mobile operating systems are more secure than desktop operating systems due to better privilege separation. It's less likely that a rogue app will steal all your TOTP codes on a mobile OS because they all tend to sandbox apps from each other. Also, a lot of phones come with hardware security modules that can encrypt your TOTP codes when the phone is locked. The only better option is to use a dedicated hardware security token (but don't buy YubiKey, the enemy of your freedom.)
I swear to god these open source developers just abandonging their documentation and website randomly
I will give KeePassXC a try even though I've been using KeePass for the last couple of years without problems
speaking of lazy FOSS retards, I read on FreeOTP's github site that they were "gonna implement backup functionality" (posted 25 july this year) but alas nothing has happened and the last commit to FreeOTP was like 2 years ago