Feature #15214
Iteration 1: Support unlocking VeraCrypt partitions in GNOME
100%
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.
Files
Subtasks
| Feature #15215: Iteration 1: Support unlocking VeraCrypt partitions in udisks | Resolved | segfault | 50 |
||
| Feature #15216: Iteration 1: Support unlocking VeraCrypt partitions in libblockdev | Resolved | segfault | 100 |
||
| Feature #15217: Iteration 1: Support unlocking VeraCrypt partitions in Disks | Resolved | segfault | 100 |
||
| Feature #15218: Iteration 1: Support unlocking VeraCrypt partitions in GVfs | Resolved | 100 |
|||
| Feature #15219: Iteration 1: Upstream unlocking VeraCrypt partitions in libblockdev | Resolved | segfault | 100 |
||
| Feature #15220: Iteration 1: Upstream unlocking VeraCrypt partitions in udisks | Resolved | 100 |
|||
| Feature #15221: Iteration 1: Upstream unlocking VeraCrypt partitions in Disks | Resolved | segfault | 100 |
||
| Feature #15222: Iteration 1: Upstream unlocking VeraCrypt partitions in GVfs | Resolved | segfault | 100 |
||
| Feature #15238: Iteration 1: Write tests for unlocking VeraCrypt partitions in GNOME | Resolved | 100 |
|||
| Feature #15247: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in libblockdev | Resolved | 100 |
|||
| Feature #15248: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in udisks | Resolved | 100 |
|||
| Feature #15249: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in Disks | Resolved | 100 |
|||
| Feature #15250: Iteration 1: Let upstream know we intend to support unlocking VeraCrypt partitions in GVfs | Resolved | 100 |
|||
| Feature #15253: Iteration 1: Backport support for unlocking VeraCrypt partitions to udisks in Stretch | Resolved | 100 |
|||
| Feature #15478: Revisit GVfs goals for iteration 1 | Resolved | 0 |
|||
| Feature #15515: Iteration 1: Backport our VeraCrypt patches to Disks in Stretch | Resolved | 100 |
|||
| Feature #15521: Iteration 1: Create Debian packages to ship our VeraCrypt patches in Tails 3.9 | Resolved | 100 |
|||
| Feature #15524: Iteration 1: Write release process documentation for custom packages | Resolved | 100 |
|||
| Bug #15630: GNOME Shell unlock dialog fails silently if udisks doesn't support PIM | Resolved | 0 |
Related issues
|
Blocks Tails - |
Resolved | 2017-12-10 |
History
#1 Updated by segfault 2018-01-22 18:13:00
- blocks
Feature #15223: Iteration 2: Support unlocking VeraCrypt file containers in GNOME added
#2 Updated by segfault 2018-01-22 22:31:54
- Description updated
#3 Updated by segfault 2018-01-25 15:26:18
- Target version changed from Tails_3.9 to Tails_3.7
#4 Updated by segfault 2018-01-25 15:57:55
- Subject changed from Support unlocking VeraCrypt partitions in GNOME to Iteration 1: Support unlocking VeraCrypt partitions in GNOME
#5 Updated by tycxtu 2018-03-30 17:06:34
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 2018-03-30 17:08:07
4 pics uploaded to show how the zuluCrypt works in Tails.
#7 Updated by segfault 2018-04-06 10:36:39
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 2018-05-10 11:09:22
- Target version changed from Tails_3.7 to Tails_3.8
#9 Updated by intrigeri 2018-06-03 13:06:08
- Status changed from Confirmed to In Progress
#10 Updated by intrigeri 2018-06-26 16:27:58
- Target version changed from Tails_3.8 to Tails_3.9
#11 Updated by intrigeri 2018-09-05 16:26:57
- Target version changed from Tails_3.9 to Tails_3.10.1
#12 Updated by segfault 2018-10-23 22:34:07
- Target version changed from Tails_3.10.1 to Tails_3.11
#13 Updated by CyrilBrulebois 2018-12-16 13:56:37
- Target version changed from Tails_3.11 to Tails_3.12
#14 Updated by anonym 2019-01-30 11:59:17
- Target version changed from Tails_3.12 to Tails_3.13
#15 Updated by CyrilBrulebois 2019-03-20 14:35:10
- Target version changed from Tails_3.13 to Tails_3.14
#16 Updated by segfault 2019-05-21 12:25:59
- Status changed from In Progress to Resolved