1 Cryptsetup 1.7.1 Release Notes
2 ==============================
4 Changes since version 1.7.0
6 * Code now uses kernel crypto API backend according to new
7 changes introduced in mainline kernel
9 While mainline kernel should contain backward compatible
10 changes, some stable series kernels do not contain fully
11 backported compatibility patches.
12 Without these patches most of cryptsetup operations
13 (like unlocking device) fail.
15 This change in cryptsetup ensures that all operations using
16 kernel crypto API works even on these kernels.
18 * The cryptsetup-reencrypt utility now properly detects removal
19 of underlying link to block device and does not remove
20 ongoing re-encryption log.
21 This allows proper recovery (resume) of reencrypt operation later.
23 NOTE: Never use /dev/disk/by-uuid/ path for reencryption utility,
24 this link disappears once the device metadata is temporarily
27 * Cryptsetup now allows special "-" (standard input) keyfile handling
28 even for TCRYPT (TrueCrypt and VeraCrypt compatible) devices.
30 * Cryptsetup now fails if there are more keyfiles specified
31 for non-TCRYPT device.
33 * The luksKillSlot command now does not suppress provided password
34 in batch mode (if password is wrong slot is not destroyed).
35 Note that not providing password in batch mode means that keyslot
36 is destroyed unconditionally.