Password management: now HOWTO revisions

Go back to topic: Password management: now HOWTO

  1. v5 anchor; v5 full version
  2. v4 anchor; v4 full version
  3. v3 anchor; v3 full version
  4. v2 anchor; v2 full version

Revision #5

Edited on
2023-09-07
Edited by user
deeplow

Revision #4

Edited on
2022-07-05
Edited by user
deeplow

Revision #3

Edited on
2021-12-20
Edited by user
arkenoi
Now, the interesting part. How to set up single KeepassXC backend to make "**accessible**" passwords available from any Qube. Now, the interesting part. How to set up single KeepassXC backend to make "**accessible**" passwords available from any Qube (maybe not *any* any, but most of general purpose ones which are not strictly domain-specific or compartmentalized due to elevated threat).

Revision #2

Edited on
2021-12-19
Edited by user
arkenoi
3. **client** setup. First, you need keepassxc to be installed in all that templates as well, because you need a binary component named keepass-xc-proxy. Then you need to define a few things: first. the **extension itself**. You may install it manually to each user, or just place the **keepassxc-browser@keepassxc.org.xpi** file to **/usr/share/mozilla/firefox/extensions**. Second, the **messaging host** reference to let the browser communicate to the proxy, the ```org.keepassxc.keepassxc_browser.json``` file. 3. **client** setup. First, you need keepassxc to be installed in all that templates as well, because you need a binary component named keepassxc-proxy. Then you need to define a few things: first. the **extension itself**. You may install it manually to each user, or just place the **keepassxc-browser@keepassxc.org.xpi** file to **/usr/share/mozilla/firefox/extensions**. Second, the **messaging host** reference to let the browser communicate to the proxy, the ```org.keepassxc.keepassxc_browser.json``` file.