Reviews for KeePassXC-Browser
KeePassXC-Browser by KeePassXC Team
Review by Romain
Rated 4 out of 5
Fonctionne très avec KeepassXC, la complétion automatique est performante même avec plusieurs identifiant, et la possibilité de choisir des champs d’identification personnalisé est la bienvenue.
449 reviews
- by Brad, a day agoRated 3 out of 5Rough around the edges. While largely functional, I routinely run into these two problems.
1) Firefox often reports that this extension is slowing down my browser and gives me a button to stop it (my browser feels locked up for 5-10 seconds when this occurs.)
2) Sometimes the extension auto fills on the browser, and sometimes I get this little red question mark on the extension icon, I have to click on that, then select it to auto form fill. I can't figure out why this happens or how to disable it.
The good news is that the entire system is great for working with yubikeys, which I love for serverless password store security. - by Firefox user 15166984, 15 days agoRated 5 out of 5Every day I get "Key exchange not successful" which forces me to restart the PC to get it working but apart from that, great tool.
I just keep the Keepass app open now and no more issues. The database locks with Windows.Developer response
posted 14 days agoJust using the Reload button from extension popup should do it, and reconnect to KeePassXC if it's started after the browser. There should be no need to restart the whole PC. - by anon, 18 days agoRated 5 out of 5
- by bantamtabak, 24 days agoRated 5 out of 5Finally the password manager I have been looking for so long.
Top. Keep it up. - by Firefox user 15078714, a month agoRated 1 out of 5浏览器点击更新密码会导致软件卡死,只能任务管理器结束运行,也是醉了,几个月的bug了!就是没人管
Developer response
posted a month ago做一个更详细的错误报告:https://github.com/keepassxreboot/keepassxc-browser/issues - by Firefox user 13421169, a month agoRated 5 out of 5
- by Firefox user 14535942, a month agoRated 5 out of 5
- by DivaSan, a month agoRated 1 out of 5Firefox browser plugin does not work anymore since I have updated to 2.7.1. On another PC with version 2.6.2 this plugin works fine. Please help.
- by TecSAR, a month agoRated 5 out of 5
- by Firefox user 13417922, a month agoRated 4 out of 5
- by Orko, a month agoRated 5 out of 5
- by Firefox user 17416689, 2 months agoRated 3 out of 5With respect to functionality the add-on works generally very well. Unfortunately, even with newest versions of Firefox, listing open port connections still shows several open connections from the keepassxc-proxy add-on to sites like googleusercontent.com, cloudfront.net, amazonaws.com and akamaitechnologies.com. Developers claim that this is a bug in Firefox beyond their control, however, the open ports are reported specifically for the keepassxc-proxy process, not for the parent firefox process. This behaviour is not particularly trust inducing.
Developer response
posted 2 months agoThis is not the first time this issue is mentioned. And still, it is a Firefox issue. Native Messaging launches a child process from the browser, and for some reason Firefox also copies the socket handles to the child process. Because of this the proxy shows connections to locations it doesn't have an access to. Some of the handles can be connections that are already terminated. The only thing the proxy does is listening for stdin and connecting to a local Unix socket by KeePassXC. Anyone can take a look at the source code and verify this, or compile a build manually where the problem still exists. - by Luciano Taurino, 2 months agoRated 3 out of 5very useful extension, works perfectly on every Operating System allowing a smooth browsing keeping safe my passwords
unfortunately, it doesn't works on Firefox snap version (nowadays snap is default on Ubuntu) - by acaminiti, 2 months agoRated 1 out of 5
- by DiscombobulaTED, 2 months agoRated 5 out of 5
- by Ankit, 2 months agoRated 4 out of 5The extension should be able to detect urls even if the database is locked. When it detects it should ask the user to unlock the database to fill the username and password. Currently I have to unlock the database even for matching the urls.
Some of the website it doesn't detect username or password fieldsDeveloper response
posted 2 months agoIt does detect URL's even when database is locked. If you click the username icon on the login field, KeePassXC will come front and asks you to unlock. After that a credential fill is done automatically. This applies if default settings are used. - by Firefox user 12370795, 3 months agoRated 1 out of 5I had the same problem, as every body else concerning the fact that, KeePassXC-Browser add-on was NOT connecting anymore with the app (database). I just downgraded the app to version 2.7.0 and now it's working fine again.
UPDATE (2 month after)
Username/password entries have mysteriously disappeared from my database, so I'm uninstalling KeePassXC and it's FF extension.Developer response
posted 3 months agoThere should be no changes between 2.7.0 and 2.7.1 concerning the browser integration. But of course we are investigating the possible issue. - by Daniel, 3 months agoRated 1 out of 5Though the plugin is connected with the database it doesn't work correctly. It provides no credentials, no matther which website i'm using.
Developer response
posted 3 months agoUsually the issue is with the entry URL's. The simpler URL, the more it matches. It's not suggested to use full URL's with path, variables etc. included. Just use addresses like https://example.com, https://subdomain.example.com or https://example.com/login.
If you cannot solve the problem, contact us on GitHub and make a new issue with details provided, thanks. - by Kraig, 3 months agoRated 1 out of 5Would not fill in any sites that I went to. There seems to be a disconnect somewhere between the extension and KeePassXC. I like the idea of KeePass, but I need a way to use it with my browser. I see lots of people have this issue. Please fix.
Developer response
posted 3 months agoUsually the issue is with the entry URL's. The simpler URL, the more it matches. It's not suggested to use full URL's with path, variables etc. included. Just use addresses like https://example.com, https://subdomain.example.com or https://example.com/login.
If you cannot solve the problem, contact us on GitHub and make a new issue with details provided, thanks. - by gmanore, 3 months agoRated 5 out of 5
- by Pjtak, 3 months agoRated 5 out of 5
- by Firefox user 15997435, 3 months agoRated 5 out of 5