KeePassXC-Browser에 대한 리뷰
KeePassXC-Browser 제작자: KeePassXC Team
Ardb 님의 리뷰
My 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.
개발자 답글
3년 전에 게시됨Probably 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.
리뷰 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 님, 2달 전
- 5점 만점에 4점Enunciate_Veggie 님, 2달 전
- 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달 전