KeePassXC-Browser에 대한 리뷰
KeePassXC-Browser 제작자: KeePassXC Team
리뷰 700개
- 5점 만점에 3점Jevgenij Zhukov 님, 7년 전Creating new entries does not work in the latest version (no blinking icon at all). It requires 2 clicks in version 1.13, but at least it works.
- 5점 만점에 5점LeDucDuBleuet 님, 7년 전
- 5점 만점에 3점Alistair George 님, 7년 전Previously was perfect, but perhaps the latest upgrade of Firefox 60.0.2 64 bit has broken it as it now doesnt fill fields since upgrade FF a couple of days ago.
- 5점 만점에 4점Firefox 사용자 14019096 님, 7년 전It does the job quite well.
Most of the time, I have to go through the credentials pop-up twice, when I load the page and since the password field is often not detected, once again by re-detecting. A minor inconvenience.
Since a recent update, it detects wrongly some fields as username fields. This problem is still present for me in version 1.1.5 yet less prevalent.
While I don't think it would be easy to do, detecting TOTP would be appreciated.
EDIT: I have to commend the team for their quick responses and action, especially with the "cpu bug" blunder.개발자 답글
7년 전에 게시됨There is no standard way to identify TOTP fields. However, it's possible to fill those using String Fields. - 5점 만점에 4점Firefox 사용자 14090590 님, 7년 전Good when it actually works as intended, since it has extremely inconsistent behavior. Losing connection to KeePassXC, pestering for inputting login credentials when there are no inputs in the page, prompting with a modal and then requiring (sometimes) to autofill manually from a dropdown in the input... Just had to disable it due to how annoying it is in its current state.
EDIT: Can confirm that 1.1.5 fixed the most annoying issue. Updating my rating to reflect the quick response to feedback and the problem being gone.개발자 답글
7년 전에 게시됨We had a bug in the last version that detected search fields as username fields. Version 1.1.5, which has just been uploaded, fixes the problem. Sorry for the inconvenience. - 5점 만점에 5점Firefox 사용자 14077593 님, 7년 전
개발자 답글
7년 전에 게시됨See https://keepassxc.org/docs/keepassxc-browser-migration/ and https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide- 5점 만점에 4점Firefox 사용자 12979101 님, 7년 전It works on most websites, but I've encountered a few exceptions here and there. "Choose own credential fields" doesn't seem to make any difference. It's cool though. Overall I'm very pleased with it. I never used a local password manager before, because I always used the build in password manager of Firefox. Using KeepassXC is much better, in my experience. I can store everything there, not just web related keys. Software serial keys, account passwords, everything. Since it is all stored locally, within my control, I feel at ease doing this. Anyway,
- 5점 만점에 5점Firefox 사용자 14051212 님, 7년 전
- 5점 만점에 5점Firefox 사용자 14049341 님, 7년 전
- 5점 만점에 4점Firefox 사용자 14027804 님, 7년 전
- 5점 만점에 5점Phil Turmel 님, 7년 전Update: Resolved! Thank you for the quick response to this bug.
Looking forward to the update -- the May 10 version is crushing Firefox when visiting the few Discourse-based forums sites I visit, including meta.discourse.org. 100% CPU on one core, Firefox UI frozen. If that helps.
In general, I *love* this plugin. - 5점 만점에 5점Firefox 사용자 14019756 님, 7년 전
- 5점 만점에 4점Firefox 사용자 14019598 님, 7년 전It works quite well, but since the last update (May 10) it makes firefox on Debian Stretch very slow, almost unusable.
- 5점 만점에 5점Firefox 사용자 14019537 님, 7년 전Marked it 5 stars as I like it. It generally works. However, with the latest update, it seems to cause heavy CPU usage due to an unresponsive script when I have Twitter open and the Twitter tab selected. Have updated to latest KeepassXC (2.3.3), have forgotten all browsers and reconnected the database. Have removed and re-added KeePassXC-Browser - same. Removing the add-on stops the heavy CPU usage and the poor browser performance on Twitter.
- 5점 만점에 5점Firefox 사용자 13676121 님, 7년 전