Is there a reason, keepassXC is not listed as multi authentification? I use an own database for it with own password.
Storing TOTP secrets in the same database as your passwords almost defeats the purpose of 2FA as all your secrets (password, TOTP) can be accessed and compromised in a single factor (your KeePass database). There’s little benefit to using 2FA if it’s not a genuine second factor. You’re better off using an MFA app with another unique password.
Yes with own db I meant a db for 2fa only. The other db will use an password I ever used anywhere.
You can just avoid storing passwords in KeePassXC and use it only for 2fa.
Also, there are still benefits of storing 2FA and passwords even in the same database. Yes, if the database leaks, you lose everything. But in other (and arguably more common) cases, only one password leaks (phishing attack, etc.). And TOTP + password in one database protect against this scenario in the same manner as split 2FA and password manager: Why does storing two-factor authentication codes in your password manager make sense? - Andy Grunwald
@TonyTheGuy For a while, that was my setup: kdbx with passwords on the desktop, kdbx with 2fa on the phone. The disadvantage of this approach is that most 2fa-only apps can’t import the kdbx database. So moving 2fa between 2fa-only apps is trivial, but moving between 2fa apps and kdbx can be annoying.
It can be a reasonable thing if you anyway need this kdbx for something else (passwords, file encryptions, passkeys, encrypted notes, etc.). If it is just about 2fa, dedicated apps like Ente are probably more convenient with the same security.
In that case you’re fine! It’s just not the most convenient solution.