Feature #9961

Add KeePassX configuration to persistence

Added by hmhiupwi 2015-08-10 21:37:55 . Updated 2017-05-22 17:33:29 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
Start date:
2015-08-10
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Password Manager
Deliverable for:

Description

Currently the only option to do so is to use dot files, and since the KeePassX configuration is in ~/.config, it makes it difficult.

Similar to all the other options in the Configure persistent volume application, I think KeePassX deserves its own persistence as well.

Subtasks

Related issues

Related to Tails - Feature #10046: Document how to save KeePassX settings using Dotfiles Resolved 2015-08-15

History

#1 Updated by intrigeri 2015-08-11 01:03:00

  • Status changed from New to Rejected

> Currently the only option to do so is to use dot files,

This is not correct: by default the KeePassX database is stored in /home/amnesia/Persistent/keepassx.kdb.
https://tails.boum.org/doc/encryption_and_privacy/manage_passwords/ documents how to use it this way.

#2 Updated by sajolida 2015-08-11 04:12:13

Feel free to propose improvements to the documentation if you think this is not clear enough. Explain better how you understood and how it failed might help us.

#3 Updated by hmhiupwi 2015-08-11 14:02:23

I am not talking about the database. I am talking about the configuration file for KeePassX that is located at ~/.config/keepassx/config.ini

#4 Updated by sajolida 2015-08-12 10:22:24

  • Status changed from Rejected to New
  • Assignee set to hmhiupwi
  • QA Check set to Info Needed
  • Type of work changed from Code to Research

Ah, sorry for the misunderstanding! Now I understand (and your description of the ticket is accurate).

Personally, I’m using KeePassX everyday to work on Tails and I never felt the need to save this file. I’m not questioning the fact that it might be important to you but I’m wondering whether it really deserves a dedicated persistence feature. Probably another solution would be to save it through the Dotfiles persistence feature, and we could explain how to do this in the KeePassX documentation. This would be more suitable if this feature is only of interest to few people.

See https://tails.boum.org/doc/first_steps/persistence/configure/#dotfiles

So, to understand better the use cases behind this, could you make a list of settings that can be saved in this file and that are relevant in the context of Tails? So we can get a better idea of how critical they are for the majority of our users…

#5 Updated by hmhiupwi 2015-08-14 15:18:35

The few settings I think are relevant to tails is:

  • Automatically save database…
    • To prevent lost of data due to shutdown, etc.
  • Security settings

I personally wanted to persist my “Global Auto-Type Shortcut” keybind, for convenience.

I will test out using dotfiles persistence to achieve this and report back.

#6 Updated by hmhiupwi 2015-08-14 15:48:08

I have tested out using dotfiles persistence to persist keepassx configuration, and it works.

Perhaps we have can modify the keepassx documentation to include a section regarding configuration persistence, or a link to the dotfiles persistence (or both).

#7 Updated by sajolida 2015-08-15 05:52:46

  • related to Feature #10046: Document how to save KeePassX settings using Dotfiles added

#8 Updated by sajolida 2015-08-15 05:54:02

  • Status changed from New to Rejected
  • Assignee deleted (hmhiupwi)
  • QA Check deleted (Info Needed)

Thanks for following-up on this. So yes, I really think that this doesn’t deserve a specific persistence feature if dotfiles work.

I created a different ticket to document how to use Dotfiles to persist the KeePassX configuration. See Feature #10046. Feel free to assign you this ticket.

#9 Updated by sajolida 2017-05-22 17:33:29

  • Affected tool set to Password Manager