Feature #15219

Iteration 1: Upstream unlocking VeraCrypt partitions in libblockdev

Added by segfault 2018-01-22 18:01:22 . Updated 2018-03-26 16:10:13 .

Status:
Resolved
Priority:
Normal
Assignee:
segfault
Category:
Target version:
Tails_3.7
Start date:
2018-01-25
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:
299

Description

Subtasks

Related issues

Blocked by Tails - Feature #15216: Iteration 1: Support unlocking VeraCrypt partitions in libblockdev Resolved 2018-01-22

History

#1 Updated by segfault 2018-01-22 18:02:28

#2 Updated by segfault 2018-01-22 18:03:03

  • blocked by Feature #15216: Iteration 1: Support unlocking VeraCrypt partitions in libblockdev added

#3 Updated by segfault 2018-01-25 13:22:13

  • % Done changed from 100 to 0

#4 Updated by segfault 2018-01-25 15:18:39

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

#5 Updated by segfault 2018-01-25 16:01:21

  • Subject changed from Upstream unlocking VeraCrypt partitions in libblockdev to Iteration 1: Upstream unlocking VeraCrypt partitions in libblockdev

#6 Updated by intrigeri 2018-02-26 14:57:12

  • Status changed from Confirmed to In Progress

#8 Updated by bertagaz 2018-03-14 11:32:21

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

#9 Updated by segfault 2018-03-25 18:43:58

  • Assignee changed from segfault to intrigeri
  • % Done changed from 0 to 100

The pull request was merged into libblockdev, so this is resolved. I seem to lack rights to close this ticket, could you do that intrigeri?

#10 Updated by intrigeri 2018-03-26 08:12:41

  • Assignee changed from intrigeri to segfault

> The pull request was merged into libblockdev, so this is resolved.

\o/

> I seem to lack rights to close this ticket, could you do that intrigeri?

Nobody can close this ticket because it’s marked as blocked by Feature #15216 (is that one about writing the code or about having it working in a Tails branch? if the former, do we have a ticket about having the code working in Tails?).

I’ll let you check the semantics of this relationship.

#11 Updated by segfault 2018-03-26 16:10:13

  • Status changed from In Progress to Resolved

intrigeri wrote:
> Nobody can close this ticket because it’s marked as blocked by Feature #15216

Oh, right.

> (is that one about writing the code or about having it working in a Tails branch? if the former, do we have a ticket about having the code working in Tails?).

It’s about writing the code, so I set it to “resolved”. libblockdev is not packaged in Jessie, so for backporting I will have to redo this work in udisks, which is covered by Feature #15253.