Feature #10956

Feature #11916: Update doc for 3.0

Bug #11917: Update KeePassX documentation

Document how to migrate existing KeePassX database

Added by intrigeri about 1 year ago. Updated 9 days ago.

Status:RejectedStart date:01/17/2016
Priority:ElevatedDue date:
Assignee:-% Done:

100%

Category:Persistence
Target version:Tails_3.0
QA Check: Blueprint:
Feature Branch: Easy:
Type of work:End-user documentation Affected tool:

Description

Tails 3.0 will include KeePassX 2.x, while Tails 2.x includes KeePassX 0.4.x. https://www.keepassx.org/news/2015/12/533 lets me think that some manual importation/migration step is needed.

  • Document that the old database is preserved. That's good as a backup but once people have done the migration, they can remove it.

Related issues

Related to Tails - Feature #10780: Upgrade KeePassX to 2.x Resolved 12/20/2015
Related to Tails - Bug #12369: Write a wrapper for KeePassX to open the old database if there is one but no new database Resolved 03/18/2017

Associated revisions

Revision 25d24178
Added by bertagaz 10 days ago

Wrap to keepassx to ease the migration to the new database format.

Refs: #10956

History

#1 Updated by BitingBird 9 months ago

#2 Updated by spriver 7 months ago

  • Assignee set to spriver

#3 Updated by intrigeri 7 months ago

The feature/stretch branch is now in a good enough shape for you to start this work: grab an ISO from http://nightly.tails.boum.org/build_Tails_ISO_feature-stretch/lastSuccessful/archive/, boot it, and after clicking "Login" in the Greeter, when presented with a text console, type CTRL-ALT-F2 to reach the GNOME desktop. If you find any issue with it, please first have a look at https://labs.riseup.net/code/projects/tails/issues?query_id=198, and if the issue you're seeing is not listed there, file a ticket with Target version = Tails 3.0. Thanks!

#4 Updated by louplisken 7 months ago

noob here using TAILS 2.6~rc1. So let me know where to post this to if this is the wrong place.
How do you document?

I migrated a keepassx database created in debian 8.5, in linux mint to keepassx2. There is an option to migrate an old database in the tools bar on the new x2. It's a one way magration that makes the database only usable by the new x2 version. Sorry I didn't get screenshots. All my keys work properly. Auto-fill is still wonky and haven't tried to edit the fields yet.

NOTE: Untill TAILS includes the new x2, users will have to maintain two seperate databases for their TAILS and non-TAILS OS. So can't wait to see the 3.0!

#5 Updated by sajolida 7 months ago

Thanks for the info! This is the right place I think.

#6 Updated by spriver 4 months ago

  • Parent task set to #11917

#7 Updated by intrigeri about 2 months ago

  • Description updated (diff)

#8 Updated by sajolida about 2 months ago

Today I switched to 3.0~beta1 and had to do this. Some notes:

  • DatabaseImport KeePass 1 database.
  • Enter password at prompt.
  • DatabaseSave database as, specify ~/Persistent/keepassx.kbdx.

Now, /etc/skel/.config/keepassx/config.ini still points to /home/amnesia/Persistent/keepassx.kdb so I wonder if this will work after restarting.

#9 Updated by emmapeel about 2 months ago

sajolida wrote:

Now, /etc/skel/.config/keepassx/config.ini still points to /home/amnesia/Persistent/keepassx.kdb so I wonder if this will work after restarting.

You have to browse to the file each time you boot :S


amnesia@amnesia:~/Persistent$ mkdir -p /live/persistence/TailsData_unlocked/dotfiles/.config/keepassx/
amnesia@amnesia:~/Persistent$ cp ../.config/keepassx/keepassx2.ini /live/persistence/TailsData_unlocked/dotfiles/.config/keepassx/

#10 Updated by intrigeri about 2 months ago

Now, /etc/skel/.config/keepassx/config.ini still points to /home/amnesia/Persistent/keepassx.kdb so I wonder if this will work after restarting.

You have to browse to the file each time you boot :S

Can't KeePassX be configured to always look in the new location of the file?

#11 Updated by sajolida about 1 month ago

Created #12260 to get this fixed by the Foundations team.

#12 Updated by sajolida about 1 month ago

  • Related to Bug #12260: Have KeePassX open ~/Persistent/keepassx.kbdx by default added

#13 Updated by intrigeri 11 days ago

  • Priority changed from Normal to Elevated

#14 Updated by bertagaz 10 days ago

Had a look while looking at #12260, and it doesn't seem possible to automate the move from database v1 to database v2. What we can only do is provide the new configuration file pointing to the right location for the new database file, but users will have to migrate their database by hand anyway.

So it seems we'll need a page explaining how to do the migration. We can provide a wrapper to keepassx so that users get warn and get a link to this docoumentation.

Care to take care of that?

#15 Updated by sajolida 10 days ago

  • Blocked by Bug #12369: Write a wrapper for KeePassX to open the old database if there is one but no new database added

#16 Updated by bertagaz 10 days ago

As stated, we'll see first how it goes with just fixes for #12260 and #12369. Might be that this workaround won't require any end user documentation in the end, as keepassx already explains what to do when presented an old format database.

#17 Updated by bertagaz 10 days ago

So the wrapper + config file seems to work as expected. Starting keepassx lead to open the old database, and then get notify it's in an old format. It indicates which process to follow to update it. From this it's quite easy to follow.

What may be a problem is that once you migrated your database and want to save it, you're offered by default to save it in another folder than ~/Persistent with another default name than 'keepassx'. Users may get it wrong and loose this migration (until the next reboot where they can do the migration again) if they don't explicitely tell to save it in the right folder with the right name.

So might be that we want to write some documentation in the end, and have it opened by the wrapper...

#18 Updated by sajolida 10 days ago

  • Description updated (diff)

#19 Updated by intrigeri 9 days ago

  • Related to deleted (Bug #12260: Have KeePassX open ~/Persistent/keepassx.kbdx by default)

#20 Updated by intrigeri 9 days ago

bertagaz wrote:

What may be a problem is that once you migrated your database and want to save it, you're offered by default to save it in another folder than ~/Persistent with another default name than 'keepassx'. Users may get it wrong and loose this migration (until the next reboot where they can do the migration again) if they don't explicitely tell to save it in the right folder with the right name.

This was fixed on bugfix/12260-open-keepassx-database-by-default.

So might be that we want to write some documentation in the end, and have it opened by the wrapper...

Actually not, in the end :)

#21 Updated by intrigeri 9 days ago

  • Blocked by deleted (Bug #12369: Write a wrapper for KeePassX to open the old database if there is one but no new database)

#22 Updated by intrigeri 9 days ago

  • Status changed from Confirmed to Rejected
  • Assignee deleted (spriver)
  • % Done changed from 0 to 100

#23 Updated by intrigeri 9 days ago

  • Related to Bug #12369: Write a wrapper for KeePassX to open the old database if there is one but no new database added

Also available in: Atom PDF