20
Vulnerability in KeePass allows retrieval of master password, issue is not yet fixed
(web.archive.org)
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
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.
KeePassXC could be another viable choice. Bitwarden has been free of any incidents for the eight years that I've been using it.
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.
@sxan @admin 1password is interesting since they have taken steps to make sure even full access to their servers does not mean access to contents of your vaults, since vaults are client side encrypted, not only with key derived from password, but also by another key you need to transfer between your devices for another device to be able to access the stuff.