KeePassXC

“This implementation is not spec compliant and has the potential to be blocked by relying parties.”

“This is a violation of the spec you cited above and criticized by FIDO devs here”

“Part of the appeal of keepass is that it isn't attached or involved with any other player in the space”

“KeePassXC has no remote attestation support, nor hardware-backing support”

“mostly i was missing power user features and especially ux for the browser plugin”

“password managers should not involve hosting at all, use something file-local”

“the cross platform UI on KeePassXC just didn’t look and feel good on windows”

“plain KeePassXC and an arrangement to sync the password database has served me well”

“works well if you don't mind tinkering and like independence from corporations”

“The experience is wonderful and KeePass allows me to see the private key behind the passkey”

“I store my passkeys in KeePassXC and I have absolutely no feeling of being walled into any garden”

“The point about Google or apple or your passkey manager banning your account is a reason I'm still using random passwords in Keepassxc.”

“I use KeepassXC and Syncthing. It's not a single password manager doing both the managing and syncing, but it works very well”

“it was very easy with the KeePassXC password generator parameters to generate a hex string of 32 characters”

“there are many options now for full FOSS implementations like bitwarden and KeepassXC”

“I've found a fair amount of scenarios where they don't correctly let you drop it into them.”

“KeePassXC is not for a "normal" user. It really needs to get default entry tempates out the door.”

“Keepass is also resilient to the underlying file changing while you have, say, the edit password dialog open.”

“Anyone not already using KeePass (or KeePassXC) has been doing it wrong for at least a decade.”

“browser integration almost never works for me. It never picks up the usernames, passwords for me”

“A password manager doesn't need 300 regular contributors armed with 14 LLMs”

“Just having the database isn't enough because you need the keyfile and my password to open it.”

“I'm very happy with KeepassXC on Debian and Keepass2Android on mobile. It handles TOTP accoss devices.”

“I already use KeePassXC, so I wrote a shell wrapper that fetches the key at invocation time”

“Out of the box I got a beautiful gui for seeding initial secrets while giving me a nice scriptable, non-interactive tool”

“I use passkeys from keepasxc because the native workflow for passkeys is opaque”

“KeepassXC has exportable passkeys, so you can avoid the stolen case at least.”

“I've had good experiences with KeePassXC. In addition to being able to store your passwords, it can ingest TOTP seeds.”

“nice trustworthy, FOSS KeePass ecosystem chrome on top of it (keepassxc , keepassium, etc)”

“It is genuinely great that since it’s just a file you can host it anywhere you want.”

“KeepassXC implements passkey support, but they do not implement these anti-user features”

“KeepassXC implements passkey support, but they do not implement these anti-user features.”

“I avoid storing my password database on an untrusted cloud computing platform”

“KeePassXC lets me do that, but the spec authors think it's appropriate to ban me for using it because it lets me manage my own data.”

“KeepassXC (a must-have application and dealbreaker) is still broken on Wayland.”

“KeePassXC seems completely untrustworthy at this point not only have they jumped on the AI bandwagon”

“I choose not to use a vibe coded password manager, rigorous review or not”

“if this was true why the need to point out "we're not vibe coding", and create this process around it?”

“Open source, free, local storage with versions for both Linux and Windows and mobile”

“Bitwarden is definitely more polished, and Syncthing is definitely (much) more fiddly than using Bitwarden's and Obsidian's ($5/mo) native syncing tools.”