KeepassXC and KeepassDX Guide
https://purplerabbit.gitlab.io/keepassxc-guide/Open linkView original on lemm.eeSyndicated from the fediverse. Read and engage on the original instance.
View original on lemm.ee
https://purplerabbit.gitlab.io/keepassxc-guide/Open linkView original on lemm.ee
13 replies
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.
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.
Does anyone know of a good way to sync the database to Proton drive?
https://lemdro.id/post/2083962
Edit: the github link https://github.com/hwittenborn/celeste
You can use syncthing to sync across devices.
Would you recommend DX over Keepass2Android?
I use DX, and it's a really great app with some great features like:
KeePass2Android also has those luckily
KeepassXC is pretty user friendly. I can walk anyone through using it.
KeepassXC + Syncthing is my personal solution to keep my credentials and sensitive data across my devices.