Feature #14468

Add VeraCrypt support to Tails

Added by segfault 2017-08-28 14:23:18 . Updated 2019-12-01 18:31:50 .

Status:
Resolved
Priority:
Elevated
Assignee:
segfault
Category:
Target version:
Tails_4.1
Start date:
2017-03-01
Due date:
2018-07-30
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

https://tails.boum.org/blueprint/veracrypt

Starter:
Affected tool:
Deliverable for:
299

Description

Subtasks

Feature #6337: Add support for VeraCrypt volumes in udisks Resolved segfault

100
Feature #11684: Add support for VeraCrypt volumes in GNOME Disks Resolved segfault

100
Feature #14464: Add VeraCrypt support to GNOME Files Resolved segfault

100
Feature #14469: Write Gherkin scenarios for VeraCrypt automated tests Resolved

100
Feature #14471: Write tests for VeraCrypt support in GNOME Disks Resolved

100
Feature #14473: Research development cost for adding VeraCrypt support to Tails Resolved

0
Feature #14474: Research user needs for VeraCrypt support in Tails Resolved

100
Feature #14476: Write user documentation for VeraCrypt support in Tails Resolved

100
Feature #14477: User testing and community feedback for VeraCrypt support Resolved

100
Feature #14479: Port VeraCrypt support to latest version of GNOME Resolved

100
Feature #14480: Fix bugs and UX issues of VeraCrypt support Resolved segfault

100
Feature #14742: VeraCrypt: UX & GUI design sprint Resolved segfault

100
Feature #15037: Have plans to release our VeraCrypt work in Tails Resolved

0
Feature #15043: Iteration 4: Create VeraCrypt Mounter application Resolved

100
Feature #15214: Iteration 1: Support unlocking VeraCrypt partitions in GNOME Resolved segfault

100
Feature #15223: Iteration 2: Support unlocking VeraCrypt file containers in GNOME Resolved segfault

100
Feature #15680: Icon for VeraCrypt Mounter Resolved segfault

100
Feature #15761: Organize our work wrt. GTK+ 3.24.x release schedule Resolved

100
Bug #15843: "Hidden volume" option in GNOME Shell unlock dialog doesn't work Resolved

100
Feature #15927: Document that VeraCrypt PIM will only be supported in Tails 4.0 Resolved

0
Bug #15950: udisksd erroneously logs about LUKS when manipulating VeraCrypt volume Rejected

0
Feature #15951: Inconsistency between doc and actual behaviour: "Unlock VeraCrypt Volumes opens your volume" Resolved

100
Bug #15952: VeraCrypt keyfile widget in GNOME Disks is unreachable with the keyboard Resolved

100
Bug #15954: Fix VeraCrypt volumes not being automatically opened in Nautilus when they should Resolved

100
Bug #15965: AppArmor logs denials for access to /usr/local/share/mime Resolved

100
Feature #15976: Gather success metrics on VeraCrypt integration Resolved

100

Related issues

Related to Tails - Feature #15302: Make libblockdev/cryptsetup unlock operations cancellable Confirmed 2018-02-10
Related to Tails - Feature #15450: Create LUKS2 persistent volumes by default In Progress 2018-03-23

History

#1 Updated by segfault 2017-08-28 14:51:53

  • Target version set to Tails_3.11
  • Deliverable for set to 299

#2 Updated by intrigeri 2017-08-28 16:56:33

  • Assignee set to segfault

#3 Updated by intrigeri 2017-09-01 14:22:53

  • Target version changed from Tails_3.11 to Tails_3.9

(The last Tails release before the end of the contract.)

#4 Updated by segfault 2018-01-22 19:51:28

  • Blueprint set to https://tails.boum.org/blueprint/veracrypt

#5 Updated by intrigeri 2018-01-25 14:53:17

Comments on the updated plan as encoded in Redmine:

  • Great job, congrats! Your attention to detail is appreciated :)
  • Please add pointers to the parent ticket for each iteration on the blueprint.
  • I think the tests for the first iteration (Feature #15238) should be written earlier than 3.9: ideally we would have them when we submit the code upstream or merge the code for the beta (Feature #14481), and latest at the end of June. Once Feature #15238 has been retargeted I think Feature #15214 (iteration 1) can also be moved to 3.8 or even 3.7.
  • The 3.9 milestone looks super scary because it has both stuff about finishing/polishing/releasing the first iteration and almost everything about the next 3 iterations. In order to make this view more usable I think we need a way to differentiate these 34 tickets from each other with metadata. For example, for every ticket that currently targets 3.9 (or maybe every VeryCrypt ticket actually?), you could:
    • downgrade everything about iterations 3 and 4 to Low priority
    • upgrade everything that’s about iteration 1 or a “MUST do so we can tell the sponsor we’re done” to Elevated priority
    • leave tickets that are about iteration 2 as normal priority
  • We’ll need to discuss this new timeline with the sponsor (mostly a reminder to myself).

#6 Updated by segfault 2018-02-10 11:55:28

  • related to Feature #15302: Make libblockdev/cryptsetup unlock operations cancellable added

#7 Updated by intrigeri 2018-08-09 10:42:47

  • Status changed from Confirmed to In Progress
  • Target version changed from Tails_3.9 to Tails_3.10.1

(At least some subtasks will be done post-3.9.)

#8 Updated by Anonymous 2018-08-16 11:19:55

  • related to Feature #15450: Create LUKS2 persistent volumes by default added

#9 Updated by segfault 2018-10-23 22:33:42

  • Target version changed from Tails_3.10.1 to Tails_3.11

#10 Updated by CyrilBrulebois 2018-12-16 13:55:23

  • Target version changed from Tails_3.11 to Tails_3.12

#11 Updated by anonym 2019-01-30 11:59:16

  • Target version changed from Tails_3.12 to Tails_3.13

#12 Updated by CyrilBrulebois 2019-03-20 14:35:10

  • Target version changed from Tails_3.13 to Tails_3.14

#13 Updated by CyrilBrulebois 2019-05-23 21:23:22

  • Target version changed from Tails_3.14 to Tails_3.15

#14 Updated by CyrilBrulebois 2019-07-10 10:33:59

  • Target version changed from Tails_3.15 to Tails_3.16

#15 Updated by CyrilBrulebois 2019-09-05 00:05:31

  • Target version changed from Tails_3.16 to Tails_3.17

#16 Updated by intrigeri 2019-09-12 14:25:13

  • Target version changed from Tails_3.17 to Tails_4.0

#17 Updated by intrigeri 2019-10-21 11:46:10

  • Target version changed from Tails_4.0 to Tails_4.1

#18 Updated by segfault 2019-12-01 18:31:50

  • Status changed from In Progress to Resolved