Vulnerability in KeePass allows retrieval of master password, issue is not yet fixed

admin, 1 year ago

Please, switch to Bitwarden.

sxan, 1 year ago

No.

Tge real answer is not to give control of your passwords to a third party; it's to not use crappy .Net programs.

KeePassXC is not affected.

charlesroper, 1 year ago

@sxan @admin There's now an audit of KeePassXC. Worth reading. It's sound.

https://keepassxc.org/blog/2023-04-15-audit-report/

charlesroper, 1 year ago

@sxan @admin @rysiek You can also self-host Vaultwarden. Nice and easy to do via Elast.io: https://elest.io/open-source/vaultwarden

WillowMist, 1 year ago

@charlesroper @sxan @admin @rysiek What's the difference between vaultwarden and bitwarden?

smorks, 1 year ago

@WillowMist @charlesroper @sxan @admin @rysiek from their github page: https://github.com/dani-garcia/vaultwarden

Alternative implementation of the Bitwarden server API written in Rust and compatible with upstream Bitwarden clients*, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal.

admin, 1 year ago

KeePassXC could be another viable choice. Bitwarden has been free of any incidents for the eight years that I've been using it.

sxan, 1 year ago

I just don't like having to depend on a third party, or like the idea that they have access to my keys - even encrypted. It's too many eggs in one basket, for my taste.

But lots of people like it, and I've never heard of any criticisms of it from the security community, so it's probably an acceptable choice.