Package: cryptsetup Version: 2:1.7.3-3 Severity: normal
It is a serious problem. It is quiet easy to overwrite LUKS headers at the start of the device. Especially if you create a LUKS on a whole device without partition table, and then dual-booted Windows decides to create a new empty partition table for you because there is not yet one. And now all your data are gone (if you do not have LUKS headers backups). Adding third backup block (first two being at the start and a bit after start of a device), at the end of the device (or even two times at the end), would be really useful! -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.10.0-wc1 (SMP w/12 CPU cores; PREEMPT) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (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-3 ii debconf [debconf-2.0] 1.5.60 ii dmsetup 2:1.02.137-1 ii libc6 2.24-9 Versions of packages cryptsetup recommends: ii busybox 1:1.22.0-19+b1 ii console-setup 1.163 ii initramfs-tools [linux-initramfs-tool] 0.127 ii kbd 2.0.3-2+b1 Versions of packages cryptsetup suggests: ii dosfstools 4.1-1 ii keyutils 1.5.9-9 ii liblocale-gettext-perl 1.07-3+b1 -- debconf information: cryptsetup/prerm_active_mappings: true
