c/privacy · by PolarElectric@lemm.ee · 2y

KeepassXC and KeepassDX Guide

https://purplerabbit.gitlab.io/keepassxc-guide/

72 points · 13 comments · view on lemmy.world

13 Comments

DemBoSain@midwest.social · 6 pts · 2y (5 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.

magikmw@lemm.ee · 6 pts · 2y (2 replies)

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.

DemBoSain@midwest.social · 2 pts · 2y (1 reply)

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.

magikmw@lemm.ee · 2 pts · 2y

I honestly didn't know about formats.

I just put stuff like CC numbers and such into password or custom fields.

nodsocket@lemmy.world · 4 pts · 2y (1 reply)

[ removed ]

DemBoSain@midwest.social · 2 pts · 2y

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.

Huschke@lemmy.world · 3 pts · 2y (2 replies)

Does anyone know of a good way to sync the database to Proton drive?

RandomVideos@programming.dev · 2 pts · 2y

https://lemdro.id/post/2083962

Edit: the github link https://github.com/hwittenborn/celeste