Package: cryptsetup
Version: 2:1.7.3-4
Severity: normal
In the example below, “root” is in parentheses because I do not really
know if this mechanism works for any encrypted filesystem which is not
an encrypted root filesystem (it does not work from my tests, but maybe
there are differences to take into account).
Example of a sentence which could be added just before the description
of the field “options”:
An encrypted (root) filesystem containing its key file can be unlocked
by the initramfs image if the value of the variable “KEYFILE_PATTERN”,
in the file “/etc/cryptsetup-initramfs/conf-hook”, matches the key file
path during the generation of the initramfs image.
-- Package-specific info:
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-8-686-pae (SMP w/1 CPU core)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cryptsetup depends on:
ii cryptsetup-bin 2:1.7.3-4
ii debconf [debconf-2.0] 1.5.61
ii dmsetup 2:1.02.137-2
ii libc6 2.24-11+deb9u3
Versions of packages cryptsetup recommends:
ii busybox 1:1.22.0-19+b3
ii console-setup 1.164
ii initramfs-tools [linux-initramfs-tool] 0.130
ii kbd 2.0.3-2+b1
Versions of packages cryptsetup suggests:
ii dosfstools 4.1-1
pn keyutils <none>
ii liblocale-gettext-perl 1.07-3+b1
-- debconf information excluded
