合計レビュー数: 231
  • I switched from Bitwarden and I'm missing nothing.
    I use it on FirefoxPortable from PortableApps.com

    I only wish that it supported the portable version of KeePassXC from PortableApps.com

    edit:
    I could connect it to the portable KeePassXC.
    Follow this guide:
    - https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide

    More info:
    - https://portableapps.com/node/57907
    - https://github.com/keepassxreboot/keepassxc-browser/issues/559
    - https://github.com/keepassxreboot/keepassxc-browser/issues/456

    edit 2: Actually, I don't think the guide really did the trick. I only changed, in the .json, keepassxc-proxy.exe to keepassxc.exe. This change was reverted automatically by the program.
    Rather, the solution was to install KeePassXC on Windows (non-portable). After uninstalling this, it again doesn't work.
    This probably happens because KeePassXC overwrites the Native Messaging host path in the registry. Be sure to enable the following setting on KeePassXC portable: Browser Integration -> Advanced -> Update native messaging manifest files at startup. If this is enabled in the normal KeePassXC installation, the registry is once again overridden.
  • Love it. I have KeePassXC and XC-Browser on Firefox and Chrome, across Win 10, Linux Mint 19.3 and Ubuntu 19.01 and it works beautifully.
  • I put 5 stars hoping to finally be able to use this extension: it doesn't work with the KeepassXC 2.5.2 version so I can't appreciate this module at its true value.

    //EDIT : it works well with Firefox too: https://github.com/keepassxreboot/keepassxc-browser/issues/751

    Thanks for this nice add-on! I recommand it.
    Please provide some more information and open a new issue at GitHub if you want this resolved. Please make sure your browser is not installed via Snap if you are using Linux.
  • A good add-on that works well. Unfortunately, it does not work with Firefox when Firefox is installed as a Snap package.
    Same applies to Chrome/Chromium. This is because Native Messaging cannot escape the sandbox and launch an external application (keepassxc-proxy) which is needed for the communication betweeen KeePassXC and the browser extension.