Critiques pour KeePassXC-Browser
KeePassXC-Browser par KeePassXC Team
717 notes
- Noté 1 sur 5par Utilisateur ou utilisatrice 14403121 de Firefox, il y a 7 ansDoes 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.Réponse du développeur
mis en ligne : il y a 7 ansThank 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. - Noté 2 sur 5par Jim, il y a 7 ansThis seldom works. I've spent over an hour (not an exaggeration) trying to get KeePassXC-Browser to store credentials for websites I frequent. It connects to KeepPassXC but cannot detect login fields even if you explicitly point them out to the extension. I might as well use KeePassXC as a standalone and constantly put my credentials on the clipboard.
Réponse du développeur
mis en ligne : il y a 7 ansIf you are having problems with sites that have username field and password field divided to a different pages, please add the URL to Site Preferences tab. - Noté 5 sur 5par Utilisateur ou utilisatrice 14354727 de Firefox, il y a 7 ans
- Noté 5 sur 5par Flengo, il y a 7 ans
- Noté 5 sur 5par Mrere, il y a 7 ans
- Noté 3 sur 5par Utilisateur ou utilisatrice 14232719 de Firefox, il y a 7 ansUPD. Please make this addon auto update connection to database, when press to icon
Réponse du développeur
mis en ligne : il y a 7 ansThe addon should be updating itself through AMO. The update notification inside the add-on is for KeePassXC. - Noté 5 sur 5par Utilisateur ou utilisatrice 13907074 de Firefox, il y a 7 ans
- Noté 5 sur 5par Utilisateur ou utilisatrice 13995350 de Firefox, il y a 7 ans
- Noté 3 sur 5par Utilisateur ou utilisatrice 13331982 de Firefox, il y a 7 ansWorks most of the time but can struggle to detect credential fields, doesn't seem to redetect them after re-connecting to the database.
Réponse du développeur
mis en ligne : il y a 7 ansPlease try the new version we just released. It fixes various issues with auto detection. If it still doesn't work, it'd be great if you could open an issue report at https://github.com/keepassxreboot/keepassxc-browser/issues . Thank you! - Noté 5 sur 5par CaesarRulezzz, il y a 7 ans
- Noté 5 sur 5par Cristian Florescu, il y a 7 ansWorks well in FF and it is good alternative for internal FF keystore crash (covered by automatic backup for keepass database).
- Noté 5 sur 5par Utilisateur ou utilisatrice 14276135 de Firefox, il y a 7 ans
- Noté 5 sur 5par ghost, il y a 7 ansit works on linux, no special character rendering issue nor dpi scaling issue like keepass mono
- Noté 5 sur 5par Anonymous user 0ecd3e, il y a 7 ansEDIT: This issue has been fixed. Props to an active development team.
An issue has been submitted on Github. Props to an active team who bothers to read bug reports.
After updating KeePassXC to 2.3.4, the extension works only if programs are opened in this specific order:
-Make sure everything is closed (browser and anything KeePassXC related)
-Open Firefox
-Then open KeePassXC
When the extension works it works wonderfully, but field detection does fail on some login pages such as the Google account one where you type in a username, then click next to type in the password.Réponse du développeur
mis en ligne : il y a 7 ansFor pages that use only username field for login, please use Site Preferences from the extension settings to add the site to the list, and enable the checkbox. - Noté 5 sur 5par nattfodd, il y a 7 ans
- Noté 4 sur 5par flosommerfeld, il y a 7 ans
- Noté 3 sur 5par Utilisateur ou utilisatrice 12402356 de Firefox, il y a 7 ans
- Noté 5 sur 5par JPLbudo, il y a 7 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 7 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 7 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 7 ans
- Noté 5 sur 5par Omega9, il y a 7 ans
- Noté 5 sur 5par Pnikosis, il y a 7 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 7 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 7 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 7 ansThere is no standard way to identify TOTP fields. However, it's possible to fill those using String Fields.