Has built in OTP so you can have separate dbs for that.
Edit:
I also just downloaded DX and it seems to not support Nextcloud, maybe other cloud services, so Keepass2Android stays for me, but I will follow it’s career with great interest.
I use Authenticator Pro on my watch so I don’t have to deal with getting my phone out when I just need a code.
Changing the default format is really all I dislike about Keepass. Can I tie a custom format to a folder for credit cards that allows quick access to the CC number? That would be worth switching.
I’m still using vanilla Keepass/KeepassDroid. Are there any advantages to switching to XC and DX?
I’ve tried them in the past, but for some reason I keep going back to vanilla.
I find XC more palatable.
Has built in OTP so you can have separate dbs for that.
Edit:
I also just downloaded DX and it seems to not support Nextcloud, maybe other cloud services, so Keepass2Android stays for me, but I will follow it’s career with great interest.
I use Authenticator Pro on my watch so I don’t have to deal with getting my phone out when I just need a code.
Changing the default format is really all I dislike about Keepass. Can I tie a custom format to a folder for credit cards that allows quick access to the CC number? That would be worth switching.
I honestly didn’t know about formats.
I just put stuff like CC numbers and such into password or custom fields.
There was a bug in vanilla that leaked your master password to other programs. XC was not affected.
https://www.cve.org/CVERecord?id=CVE-2023-24055
I remember that. I tried using the exploit on my own file, but couldn’t get it to work. I didn’t know the forks weren’t affected though.