this post was submitted on 17 Dec 2023
77 points (95.3% liked)

Privacy

31939 readers
1000 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 11 months ago (2 children)

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.

[–] [email protected] 6 points 11 months ago* (last edited 11 months ago) (1 children)

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.

[–] [email protected] 3 points 11 months ago (1 children)

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.

[–] [email protected] 3 points 11 months ago

I honestly didn't know about formats.

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

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (1 children)

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

[–] [email protected] 2 points 10 months ago

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.