Tails

#1 Updated by anonym 2017-05-16 09:51:54

• Assignee set to sajolida

Do you have an opinion here, as you came up with the current documented workflow for KeePassX + persistence?

#2 Updated by sajolida 2017-05-16 10:41:09

• related to Feature #11147: Automatically save KeePassX database after every change by default added

#3 Updated by sajolida 2017-05-16 10:47:35

• Assignee changed from sajolida to anonym
• Type of work changed from Discuss to Test

It seems like we already agreed to have this option enabled in Tails 2.2, see Feature #11147. So if it is not the case anymore in 3.0, then indeed it’s a bug in 3.0.

Regarding having a separate persistent feature for KeePassX, I’d like to skip this discussion unless we find other important scenarios that do not rely on this option. But if people want to discuss this futher, note that:

• We already document how to do this in https://tails.boum.org/doc#manage_passwords#index3h1.

• KeePassX can store its database anywhere on the file system so I’d like to hear more about whether this persistent feature would also take care of the password database, how, and whether it would need a migration path for people who have it in ~/Persistent/keepassx.kdbx right now.

So, anonym: can you test whether Feature #11147 is having a regression in 3.0?

#4 Updated by anonym 2017-05-16 15:45:13

• Target version changed from Tails_3.0 to Tails_3.2

#5 Updated by anonym 2017-05-16 15:53:39

• Tracker changed from Feature to Bug
• Subject changed from Consider adding a persistence preset for KeePassX to KeePassX lost the auto-save setting in Tails/Stretch
• Description updated
• Priority changed from Normal to Elevated
• Target version changed from Tails_3.2 to Tails_3.0~rc1

sajolida wrote:
> So, anonym: can you test whether Feature #11147 is having a regression in 3.0?

Yes, so this is actually a regression in Tails/Stretch, that will be trivial to fix. So let’s forget about all the nonsense about a persistence preset.

#6 Updated by anonym 2017-05-16 15:59:27

• Status changed from Confirmed to Fix committed
• Assignee deleted (anonym)
• % Done changed from 0 to 100
• QA Check set to Ready for QA
• Type of work changed from Test to Code

#7 Updated by intrigeri 2017-05-17 08:26:43

• QA Check changed from Ready for QA to Pass

Looks good to me. Any reason we don’t set AutoSaveOnExit=true as well?

#8 Updated by sajolida 2017-05-22 17:30:33

• Affected tool set to Password Manager

#9 Updated by intrigeri 2017-05-23 09:07:55

• Status changed from Fix committed to Resolved