KeePassXC-Browser에 대한 리뷰
KeePassXC-Browser 제작자: KeePassXC Team
Firefox 사용자 14403121 님의 리뷰
5점 만점에 1점
Firefox 사용자 14403121 님, 7년 전Does not work reliable. Need to be more stable. (Firefox-Version)
Problem: The key between the KeePassXC-Browser Add-On and the KeepasXC database (stored in the root folder) to exchange the secret data is not the same. (key: the secret key the exchange data bewteen the add-on, proxy (optional) and KeePassXC database. I compare the first digits)
This issue leads to that point, that every time the user closes Firefox and start Firefox later (say: next day or so) he has to regenerate all the connection information and login with a new name. The connection is not persistent. It's like every time before you close firefox you remove the connection info from the KeePassXC-Browser Add-On.
Same happen if i enable or disable the "Use a Proxy application bewteen KeePassXS and brwoser extension" in the advanced settings tab from KeePass. So, i think, it is not a issue of the proxy.
System: Ubuntu 18.04 LTS, Firefox 63.0, KeePassXC 2.3.1, KeePassXC-Browser Version: 1.3.0
Same happens under Ubuntu 16.04 LTS with a manuall KeePassXC Installation - because KeePassXC is not part of the regular Ubunut 16.04 distribution.
Problem: The key between the KeePassXC-Browser Add-On and the KeepasXC database (stored in the root folder) to exchange the secret data is not the same. (key: the secret key the exchange data bewteen the add-on, proxy (optional) and KeePassXC database. I compare the first digits)
This issue leads to that point, that every time the user closes Firefox and start Firefox later (say: next day or so) he has to regenerate all the connection information and login with a new name. The connection is not persistent. It's like every time before you close firefox you remove the connection info from the KeePassXC-Browser Add-On.
Same happen if i enable or disable the "Use a Proxy application bewteen KeePassXS and brwoser extension" in the advanced settings tab from KeePass. So, i think, it is not a issue of the proxy.
System: Ubuntu 18.04 LTS, Firefox 63.0, KeePassXC 2.3.1, KeePassXC-Browser Version: 1.3.0
Same happens under Ubuntu 16.04 LTS with a manuall KeePassXC Installation - because KeePassXC is not part of the regular Ubunut 16.04 distribution.
개발자 답글
7년 전에 게시됨Thank you for the review. Please ensure that you are not reusing the database identifier. It must be unique for each connection (actually we should prevent that from happening). You can try to delete the KeePassXC-Browser Settings entry from your database, and delete the connected keys from the extension too. Then make a reconnection with a new unique identifier.
리뷰 735개
- 5점 만점에 2점Firefox 사용자 19733088 님, 한 달 전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!
- 5점 만점에 1점John Hills 님, 한 달 전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."
개발자 답글
한 달 전에 게시됨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. - 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.
개발자 답글
2달 전에 게시됨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. - 5점 만점에 5점ProgramminCat 님, 2달 전
- 5점 만점에 5점Firefox 사용자 16478816 님, 2달 전
- 5점 만점에 5점Ryan Steed 님, 2달 전
- 5점 만점에 5점Firefox 사용자 19642928 님, 3달 전
- 5점 만점에 4점Enunciate_Veggie 님, 3달 전
- 5점 만점에 5점Firefox 사용자 13447327 님, 3달 전
- 5점 만점에 5점Thrillhouse 님, 3달 전
- 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.개발자 답글
4달 전에 게시됨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. - 5점 만점에 5점Firefox 사용자 18499562 님, 5달 전