prehistoric-systems/keepassxc-browser
1
0
Fork 0
mirror of https://github.com/keepassxreboot/keepassxc-browser.git synced 2026-03-11 08:54:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
KeePassXC Browser Extension
545 commits 22 branches 132 tags 16 MiB
JavaScript 74.3%
HTML 17.3%
CSS 6.1%
TypeScript 2.3%
Find a file
Bernhard Kirchen cf1c25f408 Do not overwrite keyRing element with itself 
Using KeePassXC 2.5.0 with a database created with KeePassXC 2.5.0,
decrypted messages from keepassxc-proxy contain an 'oldHash' and a
'hash' value that are equal. In that case, we must not try to replace
the database hash ID in the keyRing with itself, as it effectively leads
to the keyRing entry to be destroyed without replacement when using the
current implementation.
2019-10-21 17:29:58 +02:00
.github Update issue template 2018-09-11 09:21:30 -04:00
.tx Improve the build script 2019-04-10 14:43:50 +03:00
keepassxc-browser Do not overwrite keyRing element with itself 2019-10-21 17:29:58 +02:00
.gitignore No jQuery 2019-04-09 08:06:48 +03:00
build.js Improve the build script 2019-04-10 14:43:50 +03:00
CHANGELOG Merge branch 'develop' 2019-04-21 15:17:06 +02:00
keepassxc-protocol.md Support for displaying expired credentials 2019-05-09 08:51:50 +03:00
LICENSE Initial commit 2017-03-27 07:28:17 +03:00
package-lock.json Update package-lock.json from npm audit fix 2019-08-29 14:14:18 -07:00
package.json Improve the build script 2019-04-10 14:43:50 +03:00
README.md polished links a little bit to bring them in line 2019-06-13 21:39:18 +02:00

README.md

KeePassXC-Browser

Browser extension for KeePassXC with Native Messaging.

Based on pfn's chromeIPass. Some changes merged also from smorks' KeePassHttp-Connector.

Download and use

This browser extension was first supported in KeepassXC 2.3.0 (release end of 2017), in general it is advised to only use the latest available release.

Get the extension for Firefox or Chrome/Chromium.

Please see this document for instructions how to configure KeePassXC in order to connect the database correctly.

How it works

There are two methods which you can use KeePassXC-Browser to connect to KeePassXC:

  1. KeePassXC-Browser communicates with KeePassXC through keepassxc-proxy. The proxy handles listening to STDIN/STDOUT and transfers these messages through Unix domain sockets / named pipes to KeePassXC. This means KeePassXC can be used and started normally without inteference from Native Messaging API. KeePassXC-Browser starts only the proxy application and there's no risk of shutting down KeePassXC or losing any unsaved changes. You don't need to install keepassxc-proxy separately. It is included in the latest KeePassXC fork. Alternatively you can use keepassxc-proxy-rust as a proxy if you prefer a non-Qt solution. There's also Python and C++ versions available at keepassxc-proxy.

  2. KeePassXC-Browser communicates directly with KeePassXC via stdin/stdout. Using native messaging directly is a more secure as it ensures the traffic between KeePassXC and KeePassXC-Browser is direct. This method launches KeePassXC every time you start the browser and closes when you exit. This can cause unsaved changes not to be saved. If you use this method it's important to enable Automatically save after every change from KeePassXC's preferences. Because this option is not preferred as default it's good to test this feature with your OS and ensure KeePassXC asks to confirm any unsaved changes before exit.

Protocol

The details about the messaging protocol used with the browser extension and KeePassXC can be found here.

Translations

Translations are managed on Transifex which offers a web interface. Please join an existing language team or request a new one if there is none.