Tails

#3 Updated by intrigeri 2016-08-29 00:12:10

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 2016-09-05 16:53:00

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 2016-09-10 09:45:43

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

#8 Updated by sajolida 2017-02-08 12:43:41

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

• Database → Import KeePass 1 database.
• Enter password at prompt.
• Database → Save 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 2017-02-10 12:26:16

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 2017-02-10 12:44:06

>> 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 2017-02-24 15:00:34

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

#14 Updated by bertagaz 2017-03-18 11:26:36

Had a look while looking at Bug #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?

#16 Updated by bertagaz 2017-03-18 13:13:32

As stated, we’ll see first how it goes with just fixes for Bug #12260 and Bug #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 2017-03-18 15:08:29

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…

#20 Updated by intrigeri 2017-03-19 08:32:54

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 :)