Project

General

Profile

Feature #14468

Add VeraCrypt support to Tails

Added by segfault 11 months ago. Updated 2 days ago.

Status:
Confirmed
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
03/01/2017
Due date:
07/30/2018
% Done:

64%

QA Check:
Feature Branch:
Type of work:
Code
Starter:
Affected tool:

Subtasks

Feature #6337: Add support for VeraCrypt volumes in udisksResolvedsegfault

Feature #12276: Let udisks upstream know we intend to add VeraCrypt supportResolvedsegfault

Feature #14461: Review VeraCrypt support in udisksResolved

Feature #14462: Upstream VeraCrypt support in udisksResolved

Feature #14470: Write tests for VeraCrypt support in udisksRejectedanonym

Feature #15045: Support unlocking VeraCrypt hidden volumes via udisksResolvedsegfault

Feature #15046: Support unlocking with VeraCrypt keyfiles in udisksResolvedsegfault

Feature #11684: Add support for VeraCrypt volumes in GNOME DisksResolvedsegfault

Feature #12275: Let GNOME Disks upstream know we intend to add VeraCrypt supportResolvedsegfault

Feature #14463: Review VeraCrypt support in GNOME DisksResolved

Feature #14465: Upstream VeraCrypt support to GNOME DisksResolvedsegfault

Feature #15047: Support VeraCrypt keyfiles and hidden volumes in GNOME DisksResolvedsegfault

Feature #14464: Add VeraCrypt support to GNOME FilesConfirmedsegfault

Feature #14466: Review VeraCrypt support in GNOME FilesConfirmedsegfault

Feature #14467: Upstream VeraCrypt support in GNOME FilesIn Progresssegfault

Feature #14472: Write tests for VeraCrypt support in GNOME FilesConfirmedintrigeri

Feature #14482: Let GNOME Files upstream know we intend to add VeraCrypt supportResolved

Feature #15036: Add (mounted) VeraCrypt file containers to the places sidebarDuplicate

Feature #14469: Write Gherkin scenarios for VeraCrypt automated testsConfirmedintrigeri

Feature #14471: Write tests for VeraCrypt support in GNOME DisksConfirmedintrigeri

Feature #14473: Research development cost for adding VeraCrypt support to TailsResolved

Feature #14474: Research user needs for VeraCrypt support in TailsResolved

Feature #14826: Create survey on VeraCrypt usageResolved

Feature #14833: Point to the survey from /homeResolved

Feature #14858: Analyze the results of the VeraCrypt surveyResolved

Feature #14476: Write user documentation for VeraCrypt support in TailsIn Progresscbrownstein

Feature #14812: Update /doc/encryption_and_privacy/truecrypt to mention VeraCryptDuplicate

Feature #14477: User testing and community feedback for VeraCrypt supportConfirmedsegfault

Feature #14481: Release Beta for VeraCrypt support in TailsResolved

Feature #15589: Process community feedbackConfirmedsegfault

Feature #14479: Port VeraCrypt support to latest version of GNOMEConfirmedsegfault

Feature #14480: Fix bugs and UX issues of VeraCrypt supportConfirmedsegfault

Feature #15663: Improve error messages when unlocking a VeraCrypt volumeConfirmedsegfault

Feature #15664: Provide feedback during unlocking in GtkPlacesSidebarIn Progresssegfault

Feature #15665: Impossible to use keyfile in _~/Tor Browser_Resolved

Feature #15666: Administration password required to detach a disk image from _Disks_Rejected

Feature #15667: No VeraCrypt integration in file chooserConfirmedsegfault

Feature #15668: Add screenshot to locate Disks menu in top navigation barFix committed

Feature #15669: Avoid naming GNOME core apps by their common noun nameFix committed

Feature #15670: Improve the navigation of the VeraCrypt documentationConfirmedcbrownstein

Feature #15671: Improve how Disks is pointed to from GVfs monitorIn Progresssegfault

Feature #15676: Circle the "Unlock" button of Disks in red in the VeraCrypt docConfirmedsajolida

Feature #15677: Add a screenshot for "Disk Image Mounter" in VeraCrypt documentationConfirmedsajolida

Feature #15728: VeraCrypt Mounter: Spinner sometimes disappears too earlyConfirmedsegfault

Bug #15732: onioncircuits fails to start (permission denied error)Confirmedsegfault

Bug #15733: Unlocking TCRYPT volume sometimes shows a confusing error messageConfirmedsegfault

Bug #15734: TCRYPT containers mounted via gnome-disk-image-mounter are read-onlyConfirmedsegfault

Bug #15735: Error when mounting read-only TCRYPT volume with NTFS filesystemConfirmedsegfault

Feature #14742: VeraCrypt: UX & GUI design sprintResolvedsegfault

Feature #15037: Have plans to release our VeraCrypt work in TailsResolved

Feature #15043: Iteration 4: Create VeraCrypt Mounter applicationIn Progresssegfault

Feature #15680: Icon for VeraCrypt MounterIn Progresssegfault

Feature #15214: Iteration 1: Support unlocking VeraCrypt partitions in GNOMEIn Progresssegfault

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 GVfsIn Progresssegfault

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

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.xIn Progresssegfault

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 packagesConfirmedsegfault

Bug #15615: Iteration 1: Clarify whether we can upstream a `udisks2-tcrypt.deb` to DebianConfirmedsegfault

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

Feature #15223: Iteration 2: Support unlocking VeraCrypt file containers in GNOMEIn Progresssegfault

Feature #15044: Iteration 2: Support unlocking VeraCrypt file containers via GVfsResolved

Feature #15073: Iteration 2: Display file name in GvFS unlock dialog for file containersResolved

Feature #15224: Iteration 2: Support unlocking VeraCrypt file containers in NautilusConfirmedsegfault

Feature #15039: Iteration 2: Icon for .hc and .tc file extensionRejected

Feature #15051: Iteration 2: Associate .hc/.tc extension with VeraCryptIn Progresssegfault

Feature #15225: Iteration 2: Show unlocked VeraCrypt file containers in GtkPlacesSidebarResolved

Feature #15226: Iteration 2: Upstream support for file containers in GtkPlacesSidebarIn Progresssegfault

Feature #15245: Iteration 2: Let upstream know we intend to intend to support file containers in GtkPlacesSidebarResolved

Feature #15239: Iteration 2: Write tests for unlocking VeraCrypt file containers in GNOMEConfirmedintrigeri

Feature #15244: Iteration 2: Upstream support for unlocking VeraCrypt file containers in NautilusIn Progresssegfault

Feature #15246: Iteration 2: Let upstream know we intend to support unlocking VeraCrypt file containers in NautilusResolved

Feature #15724: Iteration 2: Upstream 0002-gtkmountoperation-Support-TCRYPT-options.patch in GTK+In Progresssegfault

Feature #15628: Consider re-enabling automounting to improve VeraCrypt UXResolved

Feature #15227: Iteration 3: Support creating and modifying VeraCrypt volumes in GNOMEConfirmedsegfault

Feature #15049: Iteration 3: Support creating and modifying VeraCrypt volumes via udisksConfirmedsegfault

Feature #15050: Iteration 3: Support creating and modifying VeraCrypt volumes in DisksConfirmedsegfault

Feature #15038: Iteration 3: Clarify which version of the partition formatting dialog of Disks we should redesignConfirmedsegfault

Feature #15229: Iteration 3: Support creating VeraCrypt file containersConfirmedsegfault

Feature #15235: Iteration 3: Find out which Disks version we will have in TailsConfirmedsegfault

Feature #15230: Iteration 3: Support creating and modifying VeraCrypt volumes in libblockdevConfirmedsegfault

Feature #15240: Iteration 3: Write tests for creating and modifying VeraCrypt volumes in GNOMEConfirmedanonym

Feature #15241: Iteration 3: Upstream creating and modifying VeraCrypt volumes via udisksConfirmedsegfault

Feature #15242: Iteration 3: Upstream creating and modifying VeraCrypt volumes in DisksConfirmedsegfault

Feature #15243: Iteration 3: Upstream creating and modifying VeraCrypt volumes in libblockdevConfirmedsegfault


Related issues

Related to Tails - Feature #15302: Make libblockdev/cryptsetup unlock operations cancellable Confirmed 02/10/2018

History

#1 Updated by segfault 11 months ago

  • Target version set to Tails_3.11

#2 Updated by intrigeri 11 months ago

  • Assignee set to segfault

#3 Updated by intrigeri 11 months ago

  • 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 6 months ago

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

#5 Updated by intrigeri 6 months ago

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 (#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 (#14481), and latest at the end of June. Once #15238 has been retargeted I think #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 5 months ago

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

Also available in: Atom PDF