1 Cryptsetup 1.3.0 Release Notes
2 ==============================
4 Changes since version 1.2.0
8 * Several userspace crypto backends support
10 cryptsetup now supports generic crypto backend interface which allows
11 compile package with various crypto libraries, these are already implemented:
13 * gcrypt (default, used in previous versions)
15 * NSS (because of missing ripemd160 it cannot provide full backward compatibility)
16 * kernel userspace API (provided by kernel 2.6.38 and above)
17 (Note that kernel userspace backend is very slow for this type of operation.
18 But it can be usefull for embedded systems, because you can avoid userspace
19 crypto library completely.)
21 Backend is selected during configure time, using --with-crypto_backend option.
23 configure --with-crypto_backend=BACKEND (gcrypt/openssl/nss/kernel) [gcrypt]
25 Note that performance checked (iterations) in LUKS header will cause that
26 real iteration time will differ with different backends.
27 (There are huge differences in speed between libraries.)
29 * Cryptsetup now automatically allocates loopback device (/dev/loop) if device
30 argument is file and not plain device.
32 This require Linux kernel 2.6.25 and above (which implements loop autoclear flag).
34 You can see backing file in cryptsetup status output if underlying device is loopback.
36 * Adds luksChangeKey command
38 cryptestup luksChangeKey --key-file <old keyfile> <new keyfile> [--key-slot X]
39 cryptestup luksChangeKey [--key-slot X] (for passphrase change)
41 This command allows passphrase/keyfile change in one step. If no key slot is
42 specified (and there is still free key slot on device) new slot is allocated before
45 If --key-slot option is specified (or there is no free slot) command will overwrite
47 WARNING: Be sure you have another slot active or header backup when using explicit
48 key slot (so you can unlock the device even after possible media failure).
50 * Adds compatible support for loop-AES encryption type in loopaesOpen command.
52 Linux dm-crypt in 2.6.38 and above supports loop-AES compatible mapping
53 (including multi-key and special CBC mode, all three modes are supported).
55 If you have raw loop-AES keyfile (text file with uuencoded per-line keys), you can
56 access loop-AES volume using
57 cryptsetup loopaesOpen <device> <name> [--key-size 128] --key-file <key-file>
59 If you are using GPG encrypted keyfile
60 gpg --decrypt <key-file> | cryptsetup loopaesOpen --key-file=- <device> <name>
62 Do not forget to specify key size. Other ciphers than AES should work but were
63 not tested. Version and hash is automatically detected according to number
66 Please note that loopAES dm-crypt mode is provided for compatibility reasons
67 (so you do not need to patch kernel and util-linux to map existing volumes)
68 but it is not, and never will be, optimized for speed.
69 It is experimental feature for now.
71 * WARNING: This is the last cryptsetup release which supports library with
72 old API (using struct crypt_options).
73 These calls are deprecated since 1.1.0 and AFAIK no application
74 is using it in recent distros. Removing compatible code will allow
75 new features to be implemented easily.
79 * Increase libcryptsetup version (loopAES change), still fully backward compatible.
80 * Fixes static build (--disable-static-cryptsetup now works properly).
81 * Supports secure data flag for device-mapper ioctl (will be in 2.6.39,
82 forcing kernel to wipe all ioctl buffers with possible key data).
83 To enable this flag you need new device-mapper library, in LVM2 2.02.84.
84 * Add copyright texts into some files and adds GPL exception allowing
85 to distribute resulting binaries linked with OpenSSL.
87 * Fix message when locking memory fails.
88 * Fix luksAddKey return code if master key is used.
89 * Update some text files in distributions.
90 * Add docs directory with Release Notes archive.
91 * Do not hardcode loopback device name in tests, use internal loopback library.