Beoordelingen voor KeePassXC-Browser
KeePassXC-Browser door KeePassXC Team
Beoordeling door rustymonkey
Waardering: 3 van 5
door rustymonkey, 7 jaar geledenWas 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.
Antwoord van ontwikkelaar
7 jaar geleden geplaatstThe 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.
744 beoordelingen
- Waardering: 5 van 5door Mark Andrew Gerads, 3 dagen geleden
- Waardering: 5 van 5door SilverAmd, 7 dagen geleden
- Waardering: 5 van 5door Firefox-gebruiker 19902880, 10 dagen geleden
- Waardering: 5 van 5door Craig, 10 dagen geleden
- Waardering: 5 van 5door Firefox-gebruiker 19882925, 21 dagen geleden
- Waardering: 5 van 5door Firefox-gebruiker 18863959, één maand geleden
- Waardering: 1 van 5door Firefox-gebruiker 14868755, één maand geledenNot able to add connected database. Nothing happens when clicking the Connect Database button. Bazzite 43 (linux) NVIDIA edition, Firefox 149, KeePassXC 2.7.12
- Waardering: 4 van 5door Saturnus, één maand geleden
- Waardering: 4 van 5door Fokeu, 2 maanden geleden
- Waardering: 5 van 5door Firefox-gebruiker 13156335, 2 maanden geledenWorks fine on my Windows 10 Firefox, and in Firefox on my CachyOS Linux install.
- Waardering: 5 van 5door Cangrejo, 3 maanden geledenBest password manager ever.
I know this depends of Keepassxc development, but it would be nice if card info can be stored. - Waardering: 5 van 5door elsenfox, 3 maanden geleden
- Waardering: 2 van 5door Firefox-gebruiker 19733088, 3 maanden geledenEigentlich 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!
- Waardering: 1 van 5door John Hills, 3 maanden geledenThe 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."
Antwoord van ontwikkelaar
3 maanden geleden geplaatstGitHub 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. - Waardering: 5 van 5door Lani, 4 maanden geledenIt seems that the path for native-messaging-hosts is hardcoded.
I want to move the file located at [~/.mozilla/native-messaging-hosts/org.keepassxc.keepassxc_browser.json] to [xdg-directory :: ~/.config/mozilla], but it fails.
help me? - Waardering: 1 van 5door Ethan, 4 maanden geledenit 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.
Antwoord van ontwikkelaar
4 maanden geleden geplaatstFirst 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. - Waardering: 5 van 5door A1, 4 maanden geleden
- Waardering: 5 van 5door ProgramminCat, 4 maanden geleden
- Waardering: 5 van 5door Xol, 4 maanden geleden
- Waardering: 5 van 5door Firefox-gebruiker 16478816, 4 maanden geleden
- Waardering: 5 van 5door Ryan Steed, 4 maanden geleden
- Waardering: 5 van 5door Firefox-gebruiker 19642928, 5 maanden geleden
- Waardering: 4 van 5door Enunciate_Veggie, 5 maanden geleden
- Waardering: 5 van 5door Firefox-gebruiker 13447327, 5 maanden geleden