Bug #16264

Consider switching from cryptsetup to cryptsetup-run

Added by CyrilBrulebois 2019-01-04 10:34:09 . Updated 2019-04-04 10:39:18 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_4.0
Start date:
2019-01-04
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This was spotted many times during a feature/buster build:

update-initramfs: Generating /boot/initrd.img-4.19.0-1-amd64
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.

Starting with buster, cryptsetup is a transitional package depending on both cryptsetup-initramfs and cryptsetup-run. The former deals with initramfs integration, which is likely not needed in Tails, and leads to the aforementioned warnings? Maybe we should switch our packages list from cryptsetup to cryptsetup-run, which contains the binaries we need? This would be:

config/chroot_local-packageslists/tails-common.list:cryptsetup

Subtasks

History

#1 Updated by intrigeri 2019-01-04 13:53:47

  • Status changed from New to Confirmed

> Maybe we should switch our packages list from cryptsetup to cryptsetup-run, which contains the binaries we need?

I suspect we actually only need cryptsetup-bin.

#2 Updated by intrigeri 2019-01-05 10:46:21

  • Assignee set to intrigeri

#3 Updated by intrigeri 2019-01-05 12:08:29

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100

Applied in changeset commit:tails|ec28190be49a460a321f03373014be449c088d14.

#4 Updated by intrigeri 2019-01-05 12:11:44

  • Status changed from Resolved to In Progress
  • Assignee changed from intrigeri to CyrilBrulebois
  • % Done changed from 100 to 50
  • QA Check set to Ready for QA

Switched to cryptsetup-bin. Please let me know if this breaks anything in the test suite: the only affected tests are, I think, the ones about persistence and the VeraCrypt ones.

#5 Updated by intrigeri 2019-04-02 08:39:05

  • Assignee deleted (CyrilBrulebois)

#6 Updated by anonym 2019-04-04 10:39:18

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

I see none of those warnings in my buildlogs, and persistance.feature passes. LGTM!