KeePassXC-Browser 的评价
KeePassXC-Browser 作者: KeePassXC Team
rustymonkey 的评价
评分 3 / 5
来自 rustymonkey, 7 年前Was really looking forward to trying this out, but I can't seem to get it to work at all.
Tested with FF 64.0 Portable, KP XC 2.3.4 Portable, and followed directions at https://keepassxc.org/docs/keepassxc-browser-migration/ , but cannot seem to get the browser to connect to the DB. Per the instructions, I've enabled browser integration for FF, but receive the following Error from the plug-in: "Cannot encrypt message or public key not found. Is native messaging or support for your browser enabled in KeePassXC?". Reload button doesn't help, nor does restarting the apps.
EDIT:
Thanks for responding. It sounds as if I need to make some changes to the FF launcher's ini file (in order to get FF Portable to work with this), but it's unclear what those changes are. After searching around a bit more, I see that others are experiencing this problem as well:
https://portableapps.com/node/57907
https://github.com/keepassxreboot/keepassxc/issues/1817
I saw some information at https://github.com/keepassxreboot/keepassxc/issues/1559#issuecomment-369508900 regarding what registry entries need to be shared, but it's unclear to me exactly what steps I need to take to get FF Portable to work with KeePass-XC portable. Could you provide a bit more information about exactly what .ini files I need to edit and with what changes?
EDIT 2: Another user commented that disabling the proxy (Tools > Settings > Browser integration > Advanced) solved the integration issues. I've tried this, and it seems to be a good workaround. The downside is that a second copy of KeePass XC launches with the proxy disabled, but at least it seems to work.
Tested with FF 64.0 Portable, KP XC 2.3.4 Portable, and followed directions at https://keepassxc.org/docs/keepassxc-browser-migration/ , but cannot seem to get the browser to connect to the DB. Per the instructions, I've enabled browser integration for FF, but receive the following Error from the plug-in: "Cannot encrypt message or public key not found. Is native messaging or support for your browser enabled in KeePassXC?". Reload button doesn't help, nor does restarting the apps.
EDIT:
Thanks for responding. It sounds as if I need to make some changes to the FF launcher's ini file (in order to get FF Portable to work with this), but it's unclear what those changes are. After searching around a bit more, I see that others are experiencing this problem as well:
https://portableapps.com/node/57907
https://github.com/keepassxreboot/keepassxc/issues/1817
I saw some information at https://github.com/keepassxreboot/keepassxc/issues/1559#issuecomment-369508900 regarding what registry entries need to be shared, but it's unclear to me exactly what steps I need to take to get FF Portable to work with KeePass-XC portable. Could you provide a bit more information about exactly what .ini files I need to edit and with what changes?
EDIT 2: Another user commented that disabling the proxy (Tools > Settings > Browser integration > Advanced) solved the integration issues. I've tried this, and it seems to be a good workaround. The downside is that a second copy of KeePass XC launches with the proxy disabled, but at least it seems to work.
开发者回应
发布于 7 年前The problem here is the Windows registry. Firefox Portable doesn't properly read the registry where the location of Native Messaging script file is defined. This would need a change to the Firefox Portable that it would allow to read Firefox registry entries outside the portable application. The only solution for this could be to use PortableApps Launcher and tweak the registry settings from there. See https://portableapps.com/manuals/PortableApps.comLauncher/topics/registry.html
EDIT: The issue #1817 is updated with the latest findings. Please continue the conversation there is possible.
EDIT: The issue #1817 is updated with the latest findings. Please continue the conversation there is possible.
734 条评价
- 评分 2 / 5来自 Firefox 用户 19733088, 4 天前Eigentlich gut, aber umständlich, funktioniert bei vielen Websites einfach mal gar nicht, das Felderkennungs-Tool zum Zuweisen ebenfalls nicht und kostet daher viel Zeit und Nerven in der Benutzung. Daher kann ich ebenso schnell und gut aus KeepassXC kopieren und einfügen und brauche mich nicht mit diesem AddOn herumschlagen; leider!
- 评分 1 / 5来自 John Hills, 11 天前The addon randomly shows errors like "KeePassXC-Browser has encountered an error: Key exchange was not successful" which means absolutely nothing to the user and does not help solve the problem in any way. It is the same as showing a message "Error: There has been an error. You're unlucky, too bad for you."
开发者回应
发布于 10 天前GitHub already has an issue about this. In short, there's no way to get details from the API why the key exchange / connection fails. I suggest you take a look at the most common error threads and our Troubleshooting Guide at GitHub. - it doesn't work when the password is on another page after the email. it always puts the wrong password from another account without even asking which account. developers, add a dropdown to ask the user from which account to take the password, don't just put any random password from any random account in the database. changing any setting didn't fix this.
开发者回应
发布于 1 个月前First of all, this shouldn't happen. There's already a dropdown selector when filling usernames or password from multiple accounts. Selector from the popup works as well. There are some settings that try to fill the password automatically for the selected username. Disabling those should help. If not, please file an issue to GitHub, thanks. - 评分 5 / 5来自 ProgramminCat, 1 个月前
- 评分 5 / 5来自 Firefox 用户 16478816, 2 个月前
- 评分 5 / 5来自 Ryan Steed, 2 个月前
- 评分 5 / 5来自 Firefox 用户 19642928, 2 个月前
- 评分 4 / 5来自 Enunciate_Veggie, 2 个月前
- 评分 5 / 5来自 Firefox 用户 13447327, 2 个月前
- 评分 5 / 5来自 Thrillhouse, 3 个月前
- Currently completely broken with more restrictive privacy configurations due to a bug (#2672) that was reported over two months ago and patched over a month ago - and still not released.
I would have thought show stopping bugs would be worth a point release, but apparently not.开发者回应
发布于 3 个月前Dear FartPie (love the nick btw), we've been collecting a bunch of various fixes and new features for the release, and it will be published soon. The bug you mentioned was not really high-priority, and not affecting many people so it didn't require a separate hotfix release. - 评分 5 / 5来自 Firefox 用户 18499562, 4 个月前
- 评分 5 / 5来自 Ender Dobra, 4 个月前