json file needed can be symlinked or copied to those directions, for example from under. Tor Browser installed via Torbrowser-launcher looks for the following (for en_US): /home//.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/Browser/.mozilla/native-messaging-hosts/įor now, the. home//tor-browser_en-US/Browser/TorBrowser/Data/Browser/.mozilla/native-messaging-hosts/ and globally from /usr/lib/mozilla/native-messaging-hosts/. tar.gz package will look for the following folders (when extracted to the home folder):
The registry entry should only include a (Default) variable and a _browser subfolder which also has a (Default) variable pointing to the actual JSON script path. Edge: HKEY_CURRENT_USER\\Software\\Microsoft\\Edge\\NativeMessagingHosts\\.Tor Browser: HKEY_CURRENT_USER\\Software\\Mozilla\\NativeMessagingHosts\\.Vivaldi: HKEY_CURRENT_USER\\Software\\Vivaldi\\NativeMessagingHosts\\.Firefox: HKEY_CURRENT_USER\\Software\\Mozilla\\NativeMessagingHosts\\.Chromium: HKEY_CURRENT_USER\\Software\\Chromium\\NativeMessagingHosts\\.Chrome: HKEY_CURRENT_USER\\Software\\Google\\Chrome\\NativeMessagingHosts\\.In this case consult the section "Other browsers".ĭepending on the operating system the _browser.json native messaging script file shoud be installed to these locations: WindowsĪppData\Local\keepassxc or to the KeePassXC directory if using portable version.Īlso there should be a registry entry found in the following location(s): When you encounter connection problems, you may have installed the extension with a fork of e.g. 1) After enabling Browser Integration and support for your browser
Make sure you have read the basic Getting Started documentation for the browser extension. Here's a general checklist for KeePassXC-Browser related connection issues.
0 kommentar(er)
