Bug #15950

udisksd erroneously logs about LUKS when manipulating VeraCrypt volume

Added by intrigeri 2018-09-13 12:13:22 . Updated 2018-09-19 06:09:10 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2018-09-13
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

E.g. I see Unlocked LUKS device /dev/loop1 as /dev/dm-0 after unlocking a VeraCrypt volume.

If this problem is specific to the backported version of our patches, well, forget it and reject this ticket.
If this problem is also present in the version we’ve upstreamed, then we should fix that.

Subtasks

History

#1 Updated by intrigeri 2018-09-13 12:23:15

  • Deliverable for changed from 308 to 299

#2 Updated by segfault 2018-09-18 20:42:46

  • Status changed from Confirmed to Rejected

That is only in our version, because I didn’t care about backporting the strings.

#3 Updated by segfault 2018-09-18 20:43:51

> That is only in our version, because I didn’t care about backporting the strings.

(the strings that were changed during the review, after I already backported everything else)

#4 Updated by segfault 2018-09-18 20:44:21

  • Assignee deleted (segfault)
  • Target version deleted (Tails_3.10.1)
  • QA Check deleted (Info Needed)
  • Type of work changed from Research to Code
  • Deliverable for deleted (299)

#5 Updated by intrigeri 2018-09-19 06:09:10

>> That is only in our version, because I didn’t care about backporting the strings.

> (the strings that were changed during the review, after I already backported everything else)

Thanks for the clarification :)