5 段階中 4.3 の評価
5 段階中 4.3 の評価
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.
- Iamaro Boxos によるレビュー (4日前)5 段階中 5 の評価It has helped make my digital life a little more convenient and a lot more secure. I no longer form the habit of reusing passwords because now I don't have to worry about typing out long difficult to read and remember passwords. I can just auto fill them. Thank you KeePassXC team.
- Firefox ユーザー 5965214 によるレビュー (7日前)5 段階中 4 の評価Latest update popped up a demand for a new permission, "Access browser activity during navigation". Why is that suddenly needed when it was not needed before?
- ARTAUD Pierre によるレビュー (21日前)5 段階中 4 の評価Addon très utiles et essentiel pour utiliser KeePassXC. la mise en ouvre est très facile. a recommander pour ceux qui souhaite + de sécurité sur leurs mots de passe (voir comment fonctionne KeePassXC)
- Firefox ユーザー 14234915 によるレビュー (1ヶ月前)5 段階中 4 の評価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
I could connect it to the portable KeePassXC.
Follow this guide:
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.
開発者の返信投稿日時: 1ヶ月前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.