KeePassXC-Browser értékelései
KeePassXC-Browser szerző: KeePassXC Team
Swiss_bRedd értékelése
Csillagos értékelés: 4 / 5
készítette: Swiss_bRedd, 5 éveEDIT: see bottom for additional (positive) impressions and alternatives.
Original Review:
This is almost perfect, but KeePassXC-Browser is having problems with certain websites which require more than a UserID and Password field.
For example, on the American Airlines site, a username, *last name* and PW are required. While KeePassXC allows me to enter additional attributes like "Last Name: Doe" into advanced, there does not seem to be a way to invoke pasting it into the form.
Even If one uses the "choose custom login fields" there is no way to set the last name field as one of the options . . .
Ah, well. At least there is auto-type! :-)
EDIT: The developer is fantastically responsive, as seen below (and I was also e-mail directly with further comments, a nice touch!). I pointed out the built-in documentation (of KeePassXC) is missing the "KPH:" detail (required in KeePassXC-**Browser**) given in the response (but *is* shown in the online docs which I had not yet read).
Hopefully the built-in docs and online docs become better synchronized.
If you anyone still has problems with KeePassXC-Browser, it seems there are other Firefox add-ons which can connect to KeePassXC such as "KeePassHttp-Connector."
Also, standalone add-ons such as "Owl" (not yet reviewed, but much newer than...) or "KeePass Tusk" make the promise of not needing to install a connector to KeePassXC in the first place.
Original Review:
This is almost perfect, but KeePassXC-Browser is having problems with certain websites which require more than a UserID and Password field.
For example, on the American Airlines site, a username, *last name* and PW are required. While KeePassXC allows me to enter additional attributes like "Last Name: Doe" into advanced, there does not seem to be a way to invoke pasting it into the form.
Even If one uses the "choose custom login fields" there is no way to set the last name field as one of the options . . .
Ah, well. At least there is auto-type! :-)
EDIT: The developer is fantastically responsive, as seen below (and I was also e-mail directly with further comments, a nice touch!). I pointed out the built-in documentation (of KeePassXC) is missing the "KPH:" detail (required in KeePassXC-**Browser**) given in the response (but *is* shown in the online docs which I had not yet read).
Hopefully the built-in docs and online docs become better synchronized.
If you anyone still has problems with KeePassXC-Browser, it seems there are other Firefox add-ons which can connect to KeePassXC such as "KeePassHttp-Connector."
Also, standalone add-ons such as "Owl" (not yet reviewed, but much newer than...) or "KeePass Tusk" make the promise of not needing to install a connector to KeePassXC in the first place.
Fejlesztői válasz
közzétéve: 5 éveYou can solve this by making a new attribute "KPH: LastName" to your entry. Then use Custom Login fields and select the Last name field as a String Field after selecting username/password/TOTP (obviously skip the TOTP).
735 értékelés
- Csillagos értékelés: 2 / 5készítette: Firefox felhasználó 19733088, 10 napjaEigentlich 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!
- Csillagos értékelés: 1 / 5készítette: John Hills, 17 napjaThe 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."
Fejlesztői válasz
közzétéve: 17 napjaGitHub 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. - Csillagos értékelés: 5 / 5készítette: Lani, egy hónapjaIt 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? - Csillagos értékelés: 1 / 5készítette: Ethan, egy hónapjait 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.
Fejlesztői válasz
közzétéve: egy hónapjaFirst 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. - Csillagos értékelés: 5 / 5készítette: A1, egy hónapja
- Csillagos értékelés: 5 / 5készítette: ProgramminCat, egy hónapja
- Csillagos értékelés: 5 / 5készítette: Firefox felhasználó 16478816, 2 hónapja
- Csillagos értékelés: 5 / 5készítette: Ryan Steed, 2 hónapja
- Csillagos értékelés: 5 / 5készítette: Firefox felhasználó 19642928, 2 hónapja
- Csillagos értékelés: 4 / 5készítette: Enunciate_Veggie, 2 hónapja
- Csillagos értékelés: 5 / 5készítette: Firefox felhasználó 13447327, 2 hónapja
- Csillagos értékelés: 5 / 5készítette: Thrillhouse, 3 hónapja
- 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.Fejlesztői válasz
közzétéve: 3 hónapjaDear 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. - Csillagos értékelés: 5 / 5készítette: Firefox felhasználó 18499562, 4 hónapja