keepassxc-browser VS keepassxc

A password manager can easily implement passkeys just like it implements passwords.

Though last I checked no browser had created an API for extensions to implement the passkey API. KeepassXC's implementation for example has to inject JS into every page to override `window.navigator.credentials` ( https://github.com/keepassxreboot/keepassxc-browser/pull/178... ). It works but is brittle, so a proper way through extension API would be nice.

The aforementioned uBlock Origin in all of them. Furthermore I have Dark Reader, KeePassXC-Browser, Redirector and (since very recently, but might be temporary) SponsorBlock in the browsers in which it makes sense.

It says on the troubleshooting guide, that for mac it runs off Chromium's folders, but nothing is showing up under those files. Also here is the troubleshooting guide: https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide

I just found out that the keepassxc-browser extension I use caused this (https://github.com/keepassxreboot/keepassxc-browser/issues/1452)

See: https://github.com/keepassxreboot/keepassxc-browser/issues/801

KeepassXC supports exporting, but i don't think it is released in a stable version / to the public yet:

https://github.com/keepassxreboot/keepassxc/pull/8825

If you use KeePass, make sure you use the KeePassXC variant. KeePass is dead.

https://keepassxc.org/

That's why you use the superior one, KeePassXC, as linked in the NIST link: https://github.com/keepassxreboot/keepassxc/discussions/9433

Over there, they got pissed about people constantly bugging them about it and closed the bug with the last comment reading:

for the internet, use a password manager like keepassxc with a strong password.

Another regression is that KeePassX/C AutoType doesn't work with Wayland, so now instead of a simple CTRL+V in KeePassXC, I have to separately copy and paste the user and the pass.

https://github.com/keepassxreboot/keepassxc/issues/2281