Revisiones de KeePassXC-Browser
KeePassXC-Browser por KeePassXC Team
Revisado por Ardb
Se valoró con 5 de 5
por Ardb, hace 3 añosMy previous opinion was wrong. I realized that sometimes it collides with browser's native password management. And of course the extension is very sensitive to url format, including correct protocol (https vs http) which is actually a virtue! After a bit of struggle I must say that this extension performs very well (on Debian)
I'm leaving my old opinion, maybe it will help someone:
Does not fill username nor password on almost all sites (keepass icons on user/pass fields is sometimes grayed out, sometimes not but it doesn't matter. Firefox or Chrome? Doesn't matter. Fill option doesn't work, keyboard shortcut doesn't work when database is connected (but password generator works!). No KeepassXC option in right-click menu. Surprisingly it works correctly for github (the only working site I found in my basket) which ensures me that I perfectly know what I'm doing.
I'm leaving my old opinion, maybe it will help someone:
Does not fill username nor password on almost all sites (keepass icons on user/pass fields is sometimes grayed out, sometimes not but it doesn't matter. Firefox or Chrome? Doesn't matter. Fill option doesn't work, keyboard shortcut doesn't work when database is connected (but password generator works!). No KeepassXC option in right-click menu. Surprisingly it works correctly for github (the only working site I found in my basket) which ensures me that I perfectly know what I'm doing.
Respuesta del desarrollador
publicado el hace 3 añosProbably the OS keyboard shortcuts collide with the ones in the extension's. You can modify the shortcuts from your browser. If the filling does not work, the issue seems that you are using incorrect URL's in your entries. You must define them with the simplest form possible. For example a page with URL https://www.example.com/login_page/ works great with entry URL defined as https://example.com. That works as a wildcard for https://*.example.com/*.
For Debian it's recommended to use the PPA or AppImage because the default repository often offers an old KeePassXC version.
For Debian it's recommended to use the PPA or AppImage because the default repository often offers an old KeePassXC version.
736 revisiones
- Se valoró con 4 de 5por Fokeu, hace 3 días
- Se valoró con 5 de 5por Usuario de Firefox 13156335, hace 4 díasWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Se valoró con 5 de 5por Cangrejo, hace un mesBest password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored. - Se valoró con 5 de 5por elsenfox, hace un mes
- Se valoró con 2 de 5por Usuario de Firefox 19733088, hace un mesEigentlich gut, aber umständlich, funktioniert bei vielen Websites einfach mal gar nicht, das Felderkennungs-Tool zum Zuweisen ebenfalls nicht und kostet daher viel Zeit und Nerven in der Benutzung. Daher kann ich ebenso schnell und gut aus KeepassXC kopieren und einfügen und brauche mich nicht mit diesem AddOn herumschlagen; leider!
- Se valoró con 1 de 5por John Hills, hace 2 mesesThe addon randomly shows errors like "KeePassXC-Browser has encountered an error: Key exchange was not successful" which means absolutely nothing to the user and does not help solve the problem in any way. It is the same as showing a message "Error: There has been an error. You're unlucky, too bad for you."
Respuesta del desarrollador
publicado el hace 2 mesesGitHub already has an issue about this. In short, there's no way to get details from the API why the key exchange / connection fails. I suggest you take a look at the most common error threads and our Troubleshooting Guide at GitHub. - Se valoró con 5 de 5por Lani, hace 2 mesesIt seems that the path for native-messaging-hosts is hardcoded.
I want to move the file located at [~/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc_browser.json] to [xdg-directory :: ~/.config/mozilla], but it fails.
help me? - Se valoró con 1 de 5por Ethan, hace 2 mesesit doesn't work when the password is on another page after the email. it always puts the wrong password from another account without even asking which account. developers, add a dropdown to ask the user from which account to take the password, don't just put any random password from any random account in the database. changing any setting didn't fix this.
Respuesta del desarrollador
publicado el hace 2 mesesFirst of all, this shouldn't happen. There's already a dropdown selector when filling usernames or password from multiple accounts. Selector from the popup works as well. There are some settings that try to fill the password automatically for the selected username. Disabling those should help. If not, please file an issue to GitHub, thanks. - Se valoró con 5 de 5por A1, hace 2 meses
- Se valoró con 5 de 5por ProgramminCat, hace 2 meses
- Se valoró con 5 de 5por Xol, hace 3 meses
- Se valoró con 5 de 5por Usuario de Firefox 16478816, hace 3 meses
- Se valoró con 5 de 5por Ryan Steed, hace 3 meses
- Se valoró con 5 de 5por Usuario de Firefox 19642928, hace 3 meses
- Se valoró con 4 de 5por Enunciate_Veggie, hace 3 meses
- Se valoró con 5 de 5por Usuario de Firefox 13447327, hace 3 meses
- Se valoró con 5 de 5por Thrillhouse, hace 4 meses
- Se valoró con 4 de 5por Helkin, hace 4 mesesGreat extension, love this on my Fedora 43 computer.
I would have love to have this work on Bazitte with it’s firefox in a flatpak - Se valoró con 1 de 5por FartPie, hace 4 mesesCurrently completely broken with more restrictive privacy configurations due to a bug (#2672) that was reported over two months ago and patched over a month ago - and still not released.
I would have thought show stopping bugs would be worth a point release, but apparently not.Respuesta del desarrollador
publicado el hace 4 mesesDear FartPie (love the nick btw), we've been collecting a bunch of various fixes and new features for the release, and it will be published soon. The bug you mentioned was not really high-priority, and not affecting many people so it didn't require a separate hotfix release. - Se valoró con 5 de 5por Davide, hace 4 meses
- Se valoró con 5 de 5por ESM44, hace 5 meses
- Se valoró con 5 de 5por Omar Kotb, hace 5 meses