Project

General

Profile

Bug #16264

Consider switching from cryptsetup to cryptsetup-run

Added by CyrilBrulebois 8 months ago. Updated 5 months ago.

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

100%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

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

Associated revisions

Revision ec28190b (diff)
Added by intrigeri 8 months ago

Don't install the cryptsetup initramfs integration and startup scripts (Closes: #16264)

We probably only need the binaries.

Not installing the initramfs integration will get rid of this noise:

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.

History

#1 Updated by intrigeri 8 months ago

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

  • Assignee set to intrigeri

#3 Updated by intrigeri 8 months ago

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

#4 Updated by intrigeri 8 months ago

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

  • Assignee deleted (CyrilBrulebois)

#6 Updated by anonym 5 months ago

  • 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!

Also available in: Atom PDF