Bug #11917

Update KeePassX documentation

Added by spriver 2016-11-15 13:14:20 . Updated 2017-05-22 17:31:39 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_3.0
Start date:
2016-01-17
Due date:
% Done:

100%

Feature Branch:
spriver:doc/11917-keepassx-2
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Password Manager
Deliverable for:

Description

Several steps changed:

  • creating, managing and saving a database is done via the menu entry Database (previous menu File was removed)
  • creation of a database is a bit different
  • there is no Help ▸ KeePassX Handbook… anymore, so maybe we should point to the KeePassX website
  • saving a database is a bit different (other menu name, text box name is File name and there is no Persistent entry in the left pane, but it’s in the list above)
  • a persistent saved database with the name keepassx won’t be used as default after rebooting. Apparently it’s needed to open the database manually after starting KeePassX

Subtasks

Feature #10956: Document how to migrate existing KeePassX database Rejected

100

Related issues

Blocked by Tails - Bug #12368: Design UX for migrating databases to KeePassX 2 Resolved 2017-03-18

History

#1 Updated by intrigeri 2016-11-15 13:46:28

  • Status changed from New to Confirmed

#2 Updated by spriver 2016-11-16 14:07:26

  • Description updated

#3 Updated by bertagaz 2017-03-19 08:15:29

Note that we mentioned we should explain that after the migration to Stretch/keepassx2, the old keepassx v1 database will remain in the Persistent folder. Up to them to decide what to do with it.

#4 Updated by intrigeri 2017-04-18 15:56:32

It would be nice to have an assignee here, to avoid the situation when everyone thinks somebody else will do it :)

#5 Updated by intrigeri 2017-04-18 15:57:41

  • blocked by Bug #12368: Design UX for migrating databases to KeePassX 2 added

#6 Updated by sajolida 2017-04-26 15:31:13

  • Assignee set to sajolida

#7 Updated by sajolida 2017-04-28 20:25:50

  • Assignee changed from sajolida to spriver
  • QA Check set to Ready for QA

Done that in doc/11917-keepassx-2.

spriver: do you want to have a look or should I ask someone else?

#8 Updated by sajolida 2017-04-28 20:29:09

  • Feature Branch set to doc/11917-keepassx-2

#9 Updated by spriver 2017-04-29 07:34:20

sajolida wrote:
> spriver: do you want to have a look or should I ask someone else?

Yes, I’ll do it in the next days!

#10 Updated by spriver 2017-05-01 09:48:23

  • Assignee changed from spriver to sajolida
  • Feature Branch changed from doc/11917-keepassx-2 to spriver:doc/11917-keepassx-2

Very good doc, I reproduced all steps and it’s all alright.
However, I updated the config file name that is needed for persistent storage of KeePassX, and I simplified the wording as you proposed with “Only say ‘password database’ in the first occurence of each section”.

That’s it!

#11 Updated by sajolida 2017-05-02 11:29:36

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

Ok, I’m merging into feature/stretch then.

I meant to do 688951560f but then I forgot. So cool you catched that one!

#12 Updated by sajolida 2017-05-22 17:31:39

  • Affected tool set to Password Manager