Revisiones de KeePassXC-Browser
KeePassXC-Browser por KeePassXC Team
Revisado por Myster
Se valoró con 2 de 5
por Myster, hace 5 añosJust doesn't work.
Behaviour is so random. Extension works for some sites, and completely fails for others (about 70% of the websites I browse).
The most frustrating thing, is that this green icon appears in the login field, but nothing happens when you press it.
To be noted, this is consistent whichever browser I use (FF or Chrome) and whichever OS I run (Windows 10 or Linux Mint).
I gave a KeepassXC and the browser extension a try because it looked promising, and the KeepassXC GUI is nicer to plain Keepass, but it seems I have no other option than revert to Keepass + RPC pluging + Kee browser extension.
Sad.
Behaviour is so random. Extension works for some sites, and completely fails for others (about 70% of the websites I browse).
The most frustrating thing, is that this green icon appears in the login field, but nothing happens when you press it.
To be noted, this is consistent whichever browser I use (FF or Chrome) and whichever OS I run (Windows 10 or Linux Mint).
I gave a KeepassXC and the browser extension a try because it looked promising, and the KeepassXC GUI is nicer to plain Keepass, but it seems I have no other option than revert to Keepass + RPC pluging + Kee browser extension.
Sad.
Respuesta del desarrollador
publicado el hace 5 añosThe green icon appears if your database is unlocked. It doesn't tell if you have credentials for the site or not. The popup shows an icon with a questionmark if credentials are found, and the same feature will be implemented to the Username field icon later.
If you have troubles for getting your credentials to the site, please ensure your entry URL's are correct. Sometimes pages use iframes from other subdomains for the login fields, so the safest best is to use https://example.com instead of https://loginpage.example.com. When a subdomain is removed from the entry URL it works as a wildcard, meaning https://example.com will match https://*.example.com and so on.
If you have troubles for getting your credentials to the site, please ensure your entry URL's are correct. Sometimes pages use iframes from other subdomains for the login fields, so the safest best is to use https://example.com instead of https://loginpage.example.com. When a subdomain is removed from the entry URL it works as a wildcard, meaning https://example.com will match https://*.example.com and so on.
737 revisiones
- Se valoró con 4 de 5por Saturnus, hace 8 días
- Se valoró con 4 de 5por Fokeu, hace 18 días
- Se valoró con 5 de 5por Usuario de Firefox 13156335, hace 19 díasWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Se valoró con 5 de 5por Cangrejo, hace 2 mesesBest 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 2 meses
- Se valoró con 2 de 5por Usuario de Firefox 19733088, hace 2 mesesEigentlich 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 3 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 3 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 3 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 3 meses
- Se valoró con 5 de 5por ProgramminCat, hace 3 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 4 meses
- Se valoró con 5 de 5por Usuario de Firefox 13447327, hace 4 meses
- Se valoró con 5 de 5por Thrillhouse, hace 4 meses
- Se valoró con 4 de 5por Helkin, hace 5 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 5 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 5 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 5 meses
- Se valoró con 5 de 5por ESM44, hace 5 meses