Critiques pour KeePassXC-Browser
KeePassXC-Browser par KeePassXC Team
750 notes
- Noté 5 sur 5par JPLbudo, il y a 8 ansfait parfaitement sont travail , très sécurisant et ne bug pas.et aujourd'hui toujours valable aucun problème a ce jour
- Noté 3 sur 5par Jevgenij Zhukov, il y a 8 ansCreating 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.
- Noté 1 sur 5par booblla, il y a 8 ansDoesn't work. Keep getting "Timeout or not connected to KeePassXC" error and from what I have researched. It's a common problem with no fix.
- Noté 5 sur 5par LeDucDuBleuet, il y a 8 ans
- Noté 5 sur 5par Omega9, il y a 8 ans
- Noté 5 sur 5par Pnikosis, il y a 8 ansWorks perfectly, great to have it working consistently in both Windows and Linux and Chrome and Firefox. Really convenient.
- Noté 3 sur 5par Alistair George, il y a 8 ansPreviously 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.
- Noté 4 sur 5par Utilisateur ou utilisatrice 14019096 de Firefox, il y a 8 ansIt 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.Réponse du développeur
mis en ligne : il y a 8 ansThere is no standard way to identify TOTP fields. However, it's possible to fill those using String Fields. - Noté 3 sur 5par OndraM, il y a 8 ansThis extension breaks XML rendering - see https://bugzilla.mozilla.org/show_bug.cgi?id=1401793 .
Réponse du développeur
mis en ligne : il y a 8 ansThis is a known issue and it is caused by jQuery. There's already a progress going on removing jQuery totally from the content scripts. - Noté 4 sur 5par Utilisateur ou utilisatrice 14090590 de Firefox, il y a 8 ansGood 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.Réponse du développeur
mis en ligne : il y a 8 ansWe 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. - Noté 5 sur 5par Utilisateur ou utilisatrice 12832567 de Firefox, il y a 8 ansPor el momento perfecta para integrar KeePassXC en Plasma :)
- Noté 5 sur 5par Utilisateur ou utilisatrice 14077593 de Firefox, il y a 8 ans
- Noté 4 sur 5par sgb1990, il y a 8 ansUnable to add database, so it's useless.
Edit: I was able to connect my database. I'm using Firefox Portable, which doesn't work with the default proxy. Make sure the "Use a proxy application between KeePassXC and browser extension" is unchecked, and it should connect.Réponse du développeur
mis en ligne : il y a 8 ansSee https://keepassxc.org/docs/keepassxc-browser-migration/ and https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide - Noté 4 sur 5par Utilisateur ou utilisatrice 12979101 de Firefox, il y a 8 ansIt 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,
- Noté 5 sur 5par Utilisateur ou utilisatrice 14051212 de Firefox, il y a 8 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 14049341 de Firefox, il y a 8 ans
- Noté 5 sur 5par rugk, il y a 8 ans
- Noté 4 sur 5par Utilisateur ou utilisatrice 14027804 de Firefox, il y a 8 ans
- Noté 5 sur 5par simlock, il y a 8 ansEs wäre schön, wenn die Einstellungen dieser Erweiterung auf Deutsch übersetzt würden.
- Noté 5 sur 5par Phil Turmel, il y a 8 ansUpdate: 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. - Noté 5 sur 5par Utilisateur ou utilisatrice 14019756 de Firefox, il y a 8 ans
- Noté 4 sur 5par Utilisateur ou utilisatrice 14019598 de Firefox, il y a 8 ansIt works quite well, but since the last update (May 10) it makes firefox on Debian Stretch very slow, almost unusable.
Réponse du développeur
mis en ligne : il y a 8 ansA new release that fixes the issue will be available soon. - Noté 5 sur 5par Utilisateur ou utilisatrice 14019537 de Firefox, il y a 8 ansMarked 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.
- Noté 5 sur 5par Utilisateur ou utilisatrice 13676121 de Firefox, il y a 8 ans