Project

General

Profile

Feature #15214

Feature #14468: Add VeraCrypt support to Tails

Iteration 1: Support unlocking VeraCrypt partitions in GNOME

Added by segfault over 1 year ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
01/22/2018
Due date:
07/30/2018
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

This iteration is the bare minimum for this project but also the foundation work which makes all subsequent iterations possible. It covers:

  • The unlocking of partitions, which is relevant to 65% of Tails+VeraCrypt users.
  • The opening of hidden volumes, which has a very good cost/benefit ratio and will please the users of this very popular feature.
  • The opening of legacy TrueCrypt volumes, which will come with almost no UX or backend cost.
  • The opening with keyfiles and opening of system partitions, which will also be very cheap to add to the custom dialogs that we will already have to implement for the opening of hidden volumes.

2.JPG View (28.6 KB) tycxtu, 03/30/2018 05:01 PM

3.JPG View (31.4 KB) tycxtu, 03/30/2018 05:01 PM

1.JPG View (20 KB) tycxtu, 03/30/2018 05:01 PM

4.JPG View (38.8 KB) tycxtu, 03/30/2018 05:01 PM


Subtasks

Feature #15215: Iteration 1: Support unlocking VeraCrypt partitions in udisksResolvedsegfault

Feature #15216: Iteration 1: Support unlocking VeraCrypt partitions in libblockdevResolvedsegfault

Feature #15217: Iteration 1: Support unlocking VeraCrypt partitions in DisksResolvedsegfault

Feature #15218: Iteration 1: Support unlocking VeraCrypt partitions in GVfsResolved

Feature #15219: Iteration 1: Upstream unlocking VeraCrypt partitions in libblockdevResolvedsegfault

Feature #15220: Iteration 1: Upstream unlocking VeraCrypt partitions in udisksResolved

Feature #15221: Iteration 1: Upstream unlocking VeraCrypt partitions in DisksResolvedsegfault

Feature #15222: Iteration 1: Upstream unlocking VeraCrypt partitions in GVfsResolvedsegfault

Feature #15238: Iteration 1: Write tests for unlocking VeraCrypt partitions in GNOMEResolved

Feature #15247: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in libblockdevResolved

Feature #15248: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in udisksResolved

Feature #15249: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in DisksResolved

Feature #15250: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in GVfsResolved

Feature #15253: Iteration 1: Backport support for unlocking VeraCrypt partitions to udisks in StretchResolved

Feature #15478: Revisit GVfs goals for iteration 1Resolved

Feature #15515: Iteration 1: Backport our VeraCrypt patches to Disks in StretchResolved

Feature #15521: Iteration 1: Create Debian packages to ship our VeraCrypt patches in Tails 3.9Resolved

Feature #15522: Iteration 1: Create custom Debian package for udisksResolved

Feature #15523: Iteration 1: Create custom Debian package for DisksResolved

Feature #15524: Iteration 1: Write release process documentation for custom packagesResolved

Bug #15630: GNOME Shell unlock dialog fails silently if udisks doesn't support PIMResolved


Related issues

Blocks Tails - Feature #15223: Iteration 2: Support unlocking VeraCrypt file containers in GNOME In Progress 12/10/2017

History

#1 Updated by segfault over 1 year ago

  • Blocks Feature #15223: Iteration 2: Support unlocking VeraCrypt file containers in GNOME added

#2 Updated by segfault over 1 year ago

  • Description updated (diff)

#3 Updated by segfault over 1 year ago

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

#4 Updated by segfault over 1 year ago

  • Subject changed from Support unlocking VeraCrypt partitions in GNOME to Iteration 1: Support unlocking VeraCrypt partitions in GNOME

#5 Updated by tycxtu over 1 year ago

segfault wrote:

This iteration is the bare minimum for this project but also the foundation work which makes all subsequent iterations possible. It covers:

  • The unlocking of partitions, which is relevant to 65% of Tails+VeraCrypt users.
  • The opening of hidden volumes, which has a very good cost/benefit ratio and will please the users of this very popular feature.
  • The opening of legacy TrueCrypt volumes, which will come with almost no UX or backend cost.
  • The opening with keyfiles and opening of system partitions, which will also be very cheap to add to the custom dialogs that we will already have to implement for the opening of hidden volumes.

I have to say that zuluCrypt (an open source project as the GUI of cryptsetup) will do all the job, and even more.

https://github.com/mhogomchungu/zuluCrypt
or:
http://mhogomchungu.github.io/zuluCrypt/

I had installed it and tested every encryption scheme, including dm-crypt, LUKS, truecrypt, varacrypt, it does work.

The only problem for me is when everytime Tails restarted, I had to re-install it again.

I'll be grateful if someone tell me how to "remaster"/"reconstruct" Tails.

#6 Updated by tycxtu over 1 year ago

4 pics uploaded to show how the zuluCrypt works in Tails.

#7 Updated by segfault over 1 year ago

tycxtu wrote:

I have to say that zuluCrypt (an open source project as the GUI of cryptsetup) will do all the job, and even more.

This ticket is about integrating VeraCrypt support into existing GNOME applications, in order to have a workflow that is consistent with the way other encrypted volumes are handled (for example LUKS), therefore providing a better user experience than using standalone applications.

#8 Updated by bertagaz about 1 year ago

  • Target version changed from Tails_3.7 to Tails_3.8

#9 Updated by intrigeri about 1 year ago

  • Status changed from Confirmed to In Progress

#10 Updated by intrigeri about 1 year ago

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

#11 Updated by intrigeri 11 months ago

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

#12 Updated by segfault 9 months ago

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

#13 Updated by CyrilBrulebois 7 months ago

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

#14 Updated by anonym 6 months ago

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

#15 Updated by CyrilBrulebois 4 months ago

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

#16 Updated by segfault about 2 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF