4 Device-Mapper's "crypt" target provides transparent encryption of block devices
5 using the kernel crypto API.
7 Parameters: <cipher> <key> <iv_offset> <device path> <offset>
10 Encryption cipher and an optional IV generation mode.
11 (In format cipher[:keycount]-chainmode-ivopts:ivmode).
17 /proc/crypto contains supported crypto modes
20 Key used for encryption. It is encoded as a hexadecimal number.
21 You can only use key sizes that are valid for the selected cipher.
24 Multi-key compatibility mode. You can define <keycount> keys and
25 then sectors are encrypted according to their offsets (sector 0 uses key0;
26 sector 1 uses key1 etc.). <keycount> must be a power of two.
29 The IV offset is a sector count that is added to the sector number
30 before creating the IV.
33 This is the device that is going to be used as backend and contains the
34 encrypted data. You can specify it as a path like /dev/xxx or a device
35 number <major>:<minor>.
38 Starting sector within the device where the encrypted data begins.
42 LUKS (Linux Unified Key Setup) is now the preferred way to set up disk
43 encryption with dm-crypt using the 'cryptsetup' utility, see
44 http://clemens.endorphin.org/cryptography
48 # Create a crypt device using dmsetup
49 dmsetup create crypt1 --table "0 `blockdev --getsize $1` crypt aes-cbc-essiv:sha256 babebabebabebabebabebabebabebabe 0 $1 0"
54 # Create a crypt device using cryptsetup and LUKS header with default cipher
55 cryptsetup luksFormat $1
56 cryptsetup luksOpen $1 crypt1