The Linux Unified Key Setup (LUKS) is a disk encryption specification created by Clemens Fruhwirth in 2004 and originally intended for Linux.
LUKS implements a platform-independent standard on-disk format for use in various tools. This facilitates compatibility and interoperability among different programs and operating systems, and assures that they all implement password management in a secure and documented manner.[1]
LUKS is used to encrypt a block device. The contents of the encrypted device are arbitrary, and therefore any filesystem can be encrypted, including swap partitions.[2] There is an unencrypted header at the beginning of an encrypted volume, which allows up to 8 (LUKS1) or 32 (LUKS2) encryption keys to be stored along with encryption parameters such as cipher type and key size.[3] [4]
The presence of this header is a major difference between LUKS and dm-crypt, since the header allows multiple different passphrases to be used, with the ability to change and remove them. If the header is lost or corrupted, the device will no longer be decryptable.[5]
Encryption is done with a multi-layer approach. First, the block device is encrypted using a master key. This master key is encrypted with each active user key.[6] User keys are derived from passphrases, FIDO2 security keys, TPMs or smart cards.[7] [8] The multi-layer approach allows users to change their passphrase without re-encrypting the whole block device. Key slots can contain information to verify user passphrases or other types of keys.
There are two versions of LUKS, with LUKS2 featuring resilience to header corruption, and using the Argon2 key derivation function by default, whereas LUKS1 uses PBKDF2.[9] Conversion between both versions of LUKS is possible in certain situations, but some features may not be available with LUKS1 such as Argon2. LUKS2 uses JSON as a metadata format.[10]
Available cryptographic algorithms depend on individual kernel support of the host. Libgcrypt can be used as a backend for hashing, which supports all of its algorithms. It is up to the operating system vendor to choose the default algorithm.[11] LUKS1 makes use of an anti-forensics technique called AFsplitter, allowing for secure data erasure and protection.[12]
Logical Volume Management can be used alongside LUKS.[13]
A common usage of LUKS is to provide full disk encryption, which involves encrypting the root partition of an operating system installation, which protects the operating system files from being tampered with or read by unauthorized parties.
On a Linux system, the boot partition (/boot) may be encrypted if the bootloader itself supports LUKS (e.g. GRUB). This is undertaken to prevent tampering with the Linux kernel. However, the first stage bootloader or an EFI system partition cannot be encrypted (see Full disk encryption#The boot key problem).
On mobile Linux systems, postmarketOS has developed osk-sdl to allow a full disk encrypted system to be unlocked using a touch screen.
For systems running systemd, the systemd-homed component can be used to encrypt individual home directories.[16]
The reference implementation for LUKS operates on Linux and is based on an enhanced version of cryptsetup, using dm-crypt as the disk encryption backend. Under Microsoft Windows, LUKS-encrypted disks can be used via the Windows Subsystem for Linux.[17] (Formerly, this was possible with LibreCrypt,[18] which currently has fundamental security holes,[19] [20] and which succeeded FreeOTFE, formerly DoxBox.)
DragonFly BSD supports LUKS.[21]
Several Linux distributions allow the root device to be encrypted upon OS installation. These installers include Calamares,[22] Ubiquity,[23] Debian-Installer,[24] and more.
LUKS headers are backward compatible; newer versions of LUKS are able to read headers of previous versions.[25]
| Offset | Data type | Description | ||
|---|---|---|---|---|
| 0 | 0hex | char[6] | ||
| 6 | 6hex | uint16_t | LUKS Version (0x0001 for LUKS1) | |
| 8 | 8hex | char[32] | Cipher Algorithm (e.g. "twofish", "aes") | |
| 40 | 28hex | char[32] | Cipher mode (e.g. "cbc-essiv:sha256") | |
| 72 | 48hex | char[32] | Cryptographic hash function (e.g. "sha1", "ripemd160") | |
| 104 | 68hex | uint32_t | Payload offset (position of encrypted data) in 512 byte offsets | |
| 108 | 6Chex | uint32_t | Number of key bytes | |
| 112 | 70hex | char[20] | PBKDF2 master key checksum | |
| 132 | 84hex | char[32] | PBKDF2 master key salt parameter | |
| 164 | A4hex | uint32_t | PBKDF2 master key iterations (Default: 10) | |
| 168 | A8hex | char[40] | UUID of the partition (e.g. "504c9fa7-d080-4acf-a829-73227b48fb89") | |
| 208 | D0hex | (48 Bytes) | Keyslot 1 | |
| … | ||||
| 544 | 220hex | (48 Bytes) | Keyslot 8 | |
| 592 Bytes total | ||||
| Offset | Data type | Description | |
|---|---|---|---|
| 0 | uint32_t | State of keyslot: Active=0x00AC71F3; Disabled=0x0000DEAD | |
| 4 | uint32_t | PBKDF2 iteration parameter | |
| 8 | char[32] | PBKDF2 salt parameter | |
| 40 | uint32_t | Start sector of key | |
| 44 | uint32_t | Number of anti-forensic stripes (Default: 4000) | |
| 48 Bytes total | |||
LUKS2 devices begin with a binary header intended to allow recognition and fast detection by blkid, which also contains information such as checksums. All strings used in a LUKS2 header are null-terminated strings. Directly after the binary header comes the JSON area, containing the objects config (configuration), keyslots, digests, segments (describes encrypted areas on the disk), and tokens containing extra metadata.
The binary format for regular luks2 keyslots are mostly similar to their predecessor, with the addition of different per-keyslot algorithms. Another type of key exists to allow redundancy in the case that a re-encryption process is interrupted.
Cryptsetup is the reference implementation of the LUKS frontend.
To encrypt a device with the path /dev/sda1:
To unlock an encrypted device, where name is the mapped device name:
Re-encrypting a LUKS container can be done either with the cryptsetup tool itself, or with a legacy tool called cryptsetup-reencrypt. These tools can also be used to add encryption to an existing unencrypted filesystem, or remove encryption from a block device.[26]
Both methods have similar syntax: