Source: cryptsetup-udeb
Severity: normal
Tags: d-i
X-Debbugs-Cc: [email protected]
Using cryptsetup to securely wipe a device before enabling encryption, e.g.:
cryptsetup --key-file /dev/random open --type plain /path/to/device
container
fails on my system during install, using the latest weekly snapshot of Debian
testing.
Some messages are logged to the terminal and some are logged by the kernel:
device-mapper: reload ioctl on container (253:0) failed: No such file or
directory
kernel: device-mapper: table: 253:0: crypt: Error allocating crypto tfm
kernel: device-mapper: ioctl: error adding target to table.
I am executing these commands at the partitioning step, after running these
commands:
anna-install cdebconf-newt-entropy partman-crypto-dm cryptsetup-udeb
crypto-dm-modules crypto-modules
insmod /lib/modules/$(uname -r)/kernel/drivers/md/dm-crypt.ko || insmod
dm_crypt dm-crypt || modprobe dm_crypt dm-crypt
mkdir -p /run/cryptsetup
Using cryptsetup otherwise works fine, e.g. to format, open and close LUKS2
devices.
Is there another package I should install or module I should load? I tried
inserting any crypto related module I could
find without success: cbc.ko, arch/*aes*.ko, aes_generic.ko, ...
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
