Project

General

Profile

Feature #15966

Feature #14468: Add VeraCrypt support to Tails

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

Include list of device-mapper devices in debug output

Added by segfault 30 days ago. Updated 4 days ago.

Status:
Fix committed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
09/20/2018
Due date:
% Done:

100%

QA Check:
Pass
Feature Branch:
feature/15966-dm-and-loop-debug-output
Type of work:
Code
Blueprint:
Starter:
Affected tool:
WhisperBack

Description

I'm having a hard time with some bug reports regarding VeraCrypt volumes. It might help if the whisperback reports would not only include mounted volumes, but also unmounted but unlocked ones.

A useful list of unlocked devices can be retrieved with this command:

dmsetup ls --tree -o blkdevname,uuid,active,open,rw,notrunc

The list of loop devices could also be helpful:

losetup -l -O NAME,BACK-FILE,AUTOCLEAR,RO,PARTSCAN,SIZELIMIT,OFFSET

Associated revisions

Revision 93979c75 (diff)
Added by segfault 6 days ago

Add dmsetup and losetup to debugging info (refs: #15966)

Revision 971bc93f (diff)
Added by segfault 5 days ago

Add dmsetup and losetup to debugging info (refs: #15966)

Revision f9c107a5
Added by intrigeri 4 days ago

Merge remote-tracking branch 'origin/feature/15966-dm-and-loop-debug-output' into stable (Fix-committed: #15966)

History

#1 Updated by segfault 13 days ago

  • Target version set to Tails_3.10

#2 Updated by intrigeri 10 days ago

  • Assignee set to segfault
  • Parent task set to #14477
  • Affected tool set to WhisperBack

Yeah, good idea!

Implementation wise, my 2cts: I suspect lsblk --all --output <some suitable list of columns> will give you the info you need, possibly more nicely. But whatever works for you will be great :)

Regarding who shall implement this: given the need first arose as part of #14477 and I don't recall needing the requested info to debug other kinds of issues, IMO that's part of your #14477 work (sorry…). I don't see who else should feel responsible for implementing this.

#3 Updated by segfault 6 days ago

  • Assignee changed from segfault to intrigeri
  • QA Check set to Ready for QA
  • Feature Branch set to feature/15966-dm-and-loop-debug-output

intrigeri wrote:

Implementation wise, my 2cts: I suspect lsblk --all --output <some suitable list of columns> will give you the info you need, possibly more nicely.

Thanks for the suggestion, but that doesn't include dm specific information like the encryption type (e.g. CRYPT_LUKS1 or CRYPT_TCRYPT) and loop device specific information like the auto-clear property.

#4 Updated by segfault 6 days ago

  • Status changed from Confirmed to In Progress

#5 Updated by intrigeri 5 days ago

  • Assignee changed from intrigeri to segfault
  • % Done changed from 0 to 60
  • QA Check changed from Ready for QA to Dev Needed

I assume you've checked how this renders in the WhisperBack UI; I don't think it's worth the effort to actually send a bug report and asking help desk to resend it back to you.

93979c75ef4872fde6aebea2ee4dcc94646c3ce9 LGTM but it's based on devel (+ another unmerged branch), while presumably we want to ship this in 3.10 (October), not in 3.12 (January). Feel free to merge into stable (and in turn into devel) a rebased branch whose only commit on top of stable is 93979c75ef4872fde6aebea2ee4dcc94646c3ce9, rebased (i.e. essentially, cherry-pick 93979c75ef4872fde6aebea2ee4dcc94646c3ce9 on stable). Thanks!

#6 Updated by segfault 5 days ago

  • QA Check changed from Dev Needed to Ready for QA

intrigeri wrote:

I assume you've checked how this renders in the WhisperBack UI

Yes, I did.

93979c75ef4872fde6aebea2ee4dcc94646c3ce9 LGTM but it's based on devel (+ another unmerged branch), while presumably we want to ship this in 3.10 (October), not in 3.12 (January).

Right, I had merged the two branches which fixed stable to FTBFS (at least the systemd gid issue also affected stable when I tried to build it).

I now rebased on stable.

#7 Updated by segfault 4 days ago

  • Assignee changed from segfault to intrigeri

#8 Updated by intrigeri 4 days ago

  • % Done changed from 60 to 70

Code review passes, merged locally, will push once I've validated the other branches I've merged here.

#9 Updated by intrigeri 4 days ago

  • Status changed from In Progress to Fix committed
  • Assignee deleted (intrigeri)
  • % Done changed from 70 to 100
  • QA Check changed from Ready for QA to Pass

Merged!

Also available in: Atom PDF