Recenzii pentru KeePassXC-Browser
KeePassXC-Browser de KeePassXC Team
Răspuns de la KeePassXC Team
Răspunsul dezvoltatorului
postat la 4 ani în urmăThank you for the feedback. If any of these issues are not solved, please open a ticket at GitHub.
First: This sounds like the keepassxc-proxy that is transferring the messages between the extension and KeePassXC is shutdown. This might be due to anti-virus software or some other process that interferes with it. The next time this happens, check if the process is running.
Second: Please use as simple URL's as possible in your entries. If the site you're using is for example https://loginpage.example.com/login/something?yes=no, the best entry URL for this kind of page is https://loginpage.example.com/login/, https://loginpage.example.com (or just https://example.com).
Third: This means even after filling it doesn't regognize an entry from that page. Verify the page and entry URL again.
Fourth: Yes. It's very minimal. Notifications on why the filling doesn't work needs to be added so there's some indication to the user why nothing happens. If you've lost the connection totally, the icon should be gray with and X (or gray with a lock icon if database is closed).
First: This sounds like the keepassxc-proxy that is transferring the messages between the extension and KeePassXC is shutdown. This might be due to anti-virus software or some other process that interferes with it. The next time this happens, check if the process is running.
Second: Please use as simple URL's as possible in your entries. If the site you're using is for example https://loginpage.example.com/login/something?yes=no, the best entry URL for this kind of page is https://loginpage.example.com/login/, https://loginpage.example.com (or just https://example.com).
Third: This means even after filling it doesn't regognize an entry from that page. Verify the page and entry URL again.
Fourth: Yes. It's very minimal. Notifications on why the filling doesn't work needs to be added so there's some indication to the user why nothing happens. If you've lost the connection totally, the icon should be gray with and X (or gray with a lock icon if database is closed).
736 de recenzii
- Evaluat(ă) cu 4 din 5 stelede Fokeu, 7 zile în urmă
- Evaluat(ă) cu 5 din 5 stelede Utilizator Firefox 13156335, 8 zile în urmăWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Evaluat(ă) cu 5 din 5 stelede Cangrejo, o lună în urmăBest password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored. - Evaluat(ă) cu 5 din 5 stelede elsenfox, o lună în urmă
- Evaluat(ă) cu 2 din 5 stelede Utilizator Firefox 19733088, 2 luni în urmăEigentlich 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!
- Evaluat(ă) cu 1 din 5 stelede John Hills, 2 luni în urmăThe 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."
Răspunsul dezvoltatorului
postat la 2 luni în urmăGitHub 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. - Evaluat(ă) cu 5 din 5 stelede Lani, 2 luni în urmăIt 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? - Evaluat(ă) cu 1 din 5 stelede Ethan, 2 luni în urmăit 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.
Răspunsul dezvoltatorului
postat la 2 luni în urmăFirst 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. - Evaluat(ă) cu 5 din 5 stelede A1, 3 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede ProgramminCat, 3 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede Xol, 3 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede Utilizator Firefox 16478816, 3 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede Ryan Steed, 3 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede Utilizator Firefox 19642928, 3 luni în urmă
- Evaluat(ă) cu 4 din 5 stelede Enunciate_Veggie, 3 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede Utilizator Firefox 13447327, 3 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede Thrillhouse, 4 luni în urmă
- Evaluat(ă) cu 4 din 5 stelede Helkin, 4 luni în urmăGreat 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 - Evaluat(ă) cu 1 din 5 stelede FartPie, 4 luni în urmăCurrently 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.Răspunsul dezvoltatorului
postat la 4 luni în urmăDear 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. - Evaluat(ă) cu 5 din 5 stelede Davide, 4 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede ESM44, 5 luni în urmă
- Evaluat(ă) cu 5 din 5 stelede Omar Kotb, 5 luni în urmă