Project

General

Profile

Feature #14473

Feature #14468: Add VeraCrypt support to Tails

Research development cost for adding VeraCrypt support to Tails

Added by segfault 4 months ago. Updated about 9 hours ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
08/28/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

- An evaluation of the implementation cost of each feature, by
studying the GUI and backend code, and writing proof of concept
code if needed.


Related issues

Blocks Tails - Feature #14742: VeraCrypt: UX & GUI design sprint Confirmed 09/29/2017

History

#1 Updated by sajolida 3 months ago

  • Target version changed from Tails_3.5 to Tails_3.3

We need this done before the design sprint (Nov/Dec) so I'm marking this for 3.3 (November 14) instead.

#2 Updated by 110100111011 2 months ago

Hey, I'm just wondering, why is there a "development cost" associated with veracrypt support? What exactly do you mean with "adding VeraCrypt support to Tails"? Tails already supports Veracrypt:

cryptsetup --veracrypt open --type tcrypt path name

You can mount any veracrypt volume with that. Sure, a GUI for that would be nice, but this feature sounds like you want to add more than just a GUI, so I wonder what this is about?

#3 Updated by segfault 2 months ago

110100111011 wrote:

You can mount any veracrypt volume with that. Sure, a GUI for that would be nice, but this feature sounds like you want to add more than just a GUI, so I wonder what this is about?

Yes, it is already possible to use TrueCrypt and VeraCrypt volumes in Tails via cryptsetup, which we also document here. But we want integrate TC and VC support nicely into Tails, i.e. extend the graphical tools which already allow to handle other kinds of encrypted volumes (namely LUKS). This means we plan to extend GNOME Disks (#11684) and GNOME Files (#14464) to allow unlocking of TC and VC volumes. Part of this work is also to upstream these features.

#4 Updated by intrigeri 2 months ago

#5 Updated by intrigeri 2 months ago

  • Blocked by Feature #14474: Research user needs for VeraCrypt support in Tails added

#6 Updated by sajolida 2 months ago

  • Blocked by deleted (Feature #14474: Research user needs for VeraCrypt support in Tails)

#7 Updated by sajolida 2 months ago

I'm removing the blocking relationship with #14474. For me #14473 should be done in parallel with #14474 and not be blocked by it:

  • The longer we run #14474 the better quantitative results we will have. We won't have much time already before the sprint, so blocking #14473 would be problematic.
  • The idea is to arrive at the sprint with the cost (#14473) and the benefits (#14474) and combine them. Influencing the study of the costs with the benefits might be biased.
  • Having ideas of the costs of the bits that we won't do would be good anyway to sanity check and justify the final scope of the project (and possibly continue it later on).

#8 Updated by sajolida about 2 months ago

  • Description updated (diff)

Pasting in the description of this ticket how we phrased it in the proposal. That's the preparatory work we need to do before the sprint in terms of dev.

#9 Updated by anonym 27 days ago

  • Target version changed from Tails_3.3 to Tails_3.5

#10 Updated by sajolida about 9 hours ago

  • Status changed from Confirmed to Resolved
  • Assignee deleted (segfault)

Also available in: Atom PDF