KeePassXC-Browser 的評論
KeePassXC-Browser 作者: KeePassXC Team
684 筆評論
- 評價 5 分，滿分 5 分來自 Firefox 使用者 15326803，6 年前
- 評價 1 分，滿分 5 分來自 Firefox 使用者 13503710，6 年前Not working for me on Linux Firefox 68. Plugin doesn't fetch or updates passwords. Won't connect to my database. Absolutely no trust in this app!
開發者回應
張貼於 6 年前Did you install KeePassXC via Snap? Did you look at the documentation at keepassxc.org? You need to run a helper script to get it work. If you want to solve the issue, please make a new issue to GitHub. Thanks! - 評價 5 分，滿分 5 分來自 Fontana Nicola，6 年前An absolute must. I don't even know how I have survived for years without this extension. Furthermore, every new release seems to be better than the previous one, and this is good™.
- 評價 5 分，滿分 5 分來自 Diego Roberto dos Santos，6 年前
- 評價 3 分，滿分 5 分來自 Firefox 使用者 15304175，6 年前For the most part, this functions ok and I'm able to use it. Unfortunately, for some sites (such as https://cards.barclaycardus.com/) it just doesn't seem to detect the un/pw fields even after I manually select them. Barclay's site is particularly strange. When I "choose custom login fields" I get two of the "overlays" for choosing fields. I have issues on Community America Credit Union's site as well, which might have something to do with the fact that the login form "pops open" when you click in the username field. I haven't really had any issues connecting to my KP database, mostly just issues with the auto-fill/field detection. Thanks for the all the hard work though, I appreciate it. I'm sure over time these kinks will get ironed out.
EDIT: PopOS! 18.04 (so ubuntu 18.04) & Firefox 69.0.1開發者回應
張貼於 6 年前If you change your entry URL to https://barclaycardus.com/ the login iframe will be detected correctly if you fill the credentials manually from keyboard shortcut or from the context menu. CACU site didn't have any problems with the latest release, even if the login form pops open. - 評價 4 分，滿分 5 分來自 Firefox 使用者 15257496，6 年前
- 評價 5 分，滿分 5 分來自 Firefox 使用者 15256535，6 年前
- 評價 5 分，滿分 5 分來自 Firefox 使用者 14099499，6 年前
- 評價 4 分，滿分 5 分來自 Firefox 使用者 12234572，6 年前
- 評價 5 分，滿分 5 分來自 Firefox 使用者 14945702，6 年前It works well. And it's free software solution. Thanks a lot. Good bye proprietary pasword managers (e.g. LastPass :-)
- 評價 1 分，滿分 5 分來自 Firefox 使用者 15239303，6 年前Not working for me on Linux Firefox 68. Plugin doesn't fetch or updates passwords. Works in Chromium.
開發者回應
張貼於 6 年前Please make a new issue to https://github.com/keepassxreboot/keepassxc-browser/issues with some details. - 評價 5 分，滿分 5 分來自 Firefox 使用者 15005487，6 年前This is a brilliant extension for a fantastic programme - keepassxc.
Works really well. Thanks Dev. - 評價 5 分，滿分 5 分來自 Firefox 使用者 15236514，6 年前
- 評價 5 分，滿分 5 分來自 Firefox 使用者 15213422，6 年前
- 評價 1 分，滿分 5 分來自 Firefox 使用者 15200965，6 年前The plugin suddenly stopped working. The Errormessage wasn't helpful (Unsuccesful key exchange).
No way to get it back working again. So reverting to KeePass and KeePassHTTP connector. - 評價 5 分，滿分 5 分來自 Firefox 使用者 14859916，6 年前doesn't work on waterfox, shows me this: Key exchange was not successful.
edit: thanks, i just copied the "native-messaging-hosts" file from ~/.mozilla/ to ~/.waterfox/ and the problem is solved!開發者回應
張貼於 6 年前You'll have to do a manual install for Waterfox. See https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide - 評價 5 分，滿分 5 分來自 Firefox 使用者 14533652，6 年前
- 評價 5 分，滿分 5 分來自 Firefox 使用者 15148651，6 年前
- 評價 4 分，滿分 5 分來自 Dario Panico，6 年前
開發者回應
張貼於 6 年前For these kind of sites you can use the keyboard shortcut or context menu to fill the username first. Alternatively you can enable "Username-only detection" from extension's Site Preferences settings for certain pages.- 評價 4 分，滿分 5 分來自 Firefox 使用者 15121042，6 年前I have "key exchange was not successful" with keepass 2.4.3 on Linux Mint 18.3 Sylvia and Firefox 67.0.4. Connect button does nothing. What should I do?
P.S. I don't have this problem with 2.4.3 on Linux Mint 19.1 Tessa and Firefox 66.0.1.開發者回應
張貼於 6 年前Try to remove the connections from KeePassXC and the extension. Then try to reconnect again. If it doesn't help, create an issue with more details to GitHub. Thanks.