Misplaced Pages

dm-crypt is a transparent block device encryption subsystem in Linux kernel versions 2.6 and later and in DragonFly BSD. It is part of the device mapper (dm) infrastructure, and uses cryptographic routines from the kernel's Crypto API. Unlike its predecessor cryptoloop, dm-crypt was designed to support advanced modes of operation, such as XTS, LRW and ESSIV, in order to avoid watermarking attacks. In addition to that, dm-crypt addresses some reliability problems of cryptoloop.

dm-crypt is implemented as a device mapper target and may be stacked on top of other device mapper transformations. It can thus encrypt whole disks (including removable media), partitions, software RAID volumes, logical volumes, as well as files. It appears as a block device, which can be used to back file systems, swap or as an LVM physical volume.

Some Linux distributions support the use of dm-crypt on the root file system. These distributions use initrd to prompt the user to enter a passphrase at the console, or insert a smart card prior to the normal boot process.

Frontends

The dm-crypt device mapper target resides entirely in kernel space, and is only concerned with encryption of the block device – it does not interpret any data itself. It relies on user space front-ends to create and activate encrypted volumes, and manage authentication. At least two frontends are currently available: cryptsetup and cryptmount.

cryptsetup

cryptsetup

Original author(s)	Jana Saout, Clemens Fruhwirth, Milan Broz
Stable release	2.7.5 / 3 September 2024; 3 months ago (2024-09-03)
Repository	https://gitlab.com/cryptsetup/cryptsetup
Written in	C
Operating system	Unix-like
Platform	x86, x86-64, ARMv8, ARMv7, ppc64le, MIPS
Size	7 MB
Available in	16 languages
List of languagesEnglish, Portuguese, Chinese (Simplified), Czech, Danish, Dutch, Finnish, French, German, Italian, Japanese, Polish, Russian, Spanish, Swedish, Ukrainian
Type	Disk encryption software
License	GPLv2 Sub-Libraries: LGPLv2.1+
Website	gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt

The cryptsetup command-line interface, by default, does not write any headers to the encrypted volume, and hence only provides the bare essentials: encryption settings have to be provided every time the disk is mounted (although usually employed with automated scripts), and only one key can be used per volume; the symmetric encryption key is directly derived from the supplied passphrase.

Because it lacks a "salt", using cryptsetup is less secure in this mode than is the case with Linux Unified Key Setup (LUKS). However, the simplicity of cryptsetup makes it useful when combined with third-party software, for example, with smart card authentication.

cryptsetup also provides commands to deal with the LUKS on-disk format. This format provides additional features such as key management and key stretching (using PBKDF2), and remembers encrypted volume configuration across reboots.

cryptmount

The cryptmount interface is an alternative to the "cryptsetup" tool that allows any user to mount and unmount a dm-crypt file system when needed, without needing superuser privileges after the device has been configured by a superuser.

Features

The fact that disk encryption (volume encryption) software like dm-crypt only deals with transparent encryption of abstract block devices gives it a lot of flexibility. This means that it can be used for encrypting any disk-backed file systems supported by the operating system, as well as swap space; write barriers implemented by file systems are preserved. Encrypted volumes can be stored on disk partitions, logical volumes, whole disks as well as file-backed disk images (through the use of loop devices with the losetup utility). dm-crypt can also be configured to encrypt RAID volumes and LVM physical volumes.

dm-crypt can also be configured to provide pre-boot authentication through an initrd, thus encrypting all the data on a computer – except the bootloader, the kernel and the initrd image itself.

When using the cipher block chaining (CBC) mode of operation with predictable initialization vectors as other disk encryption software, the disk is vulnerable to watermarking attacks. This means that an attacker is able to detect the presence of specially crafted data on the disk. To address this problem in its predecessors, dm-crypt included provisions for more elaborate, disk encryption-specific modes of operation. Support for ESSIV (encrypted salt-sector initialization vector) was introduced in Linux kernel version 2.6.10, LRW in 2.6.20 and XTS in 2.6.24. A wide-block disk encryption algorithm, Adiantum, was added in 5.0, and its AES-based cousin HCTR2 in 6.0.

The Linux Crypto API includes support for most popular block ciphers and hash functions, which are all usable with dm-crypt.

Crypted FS support include LUKS (versions 1 and 2) volumes, loop-AES, TrueCrypt/VeraCrypt (since Linux kernel 3.13), and BitLocker-encrypted NTFS (since cryptsetup 2.3.0). TrueCrypt/VeraCrypt (TCRYPT) and BitLocker (BITLK) support require the kernel userspace crypto API.

Compatibility

dm-crypt and LUKS encrypted disks can be accessed and used under MS Windows using the now defunct FreeOTFE (formerly DoxBox, LibreCrypt), provided that the filesystem used is supported by Windows (e.g. FAT/FAT32/NTFS). Encrypted ext2 and ext3 filesystems are supported by using Ext2Fsd or so-called "Ext2 Installable File System for Windows"; FreeOTFE also supports them.

Cryptsetup/LUKS and the required infrastructure have also been implemented on the DragonFly BSD operating system.

See also

• Comparison of disk encryption software

References

1. ^ Fruhwirth, Clemens (18 July 2005). "New Methods in Hard Disk Encryption" (PDF). Vienna University of Technology. Retrieved 22 August 2024.
2. Peters, Mike. "Encrypting partitions using dm-crypt and the 2.6 series kernel". Linux.com. Archived from the original on 11 July 2012. Retrieved 22 August 2024.
3. ^ W. Michael Petullo (2007-01-18). "Disk encryption in Fedora: Past, present and future". Red Hat Magazine. Archived from the original on 2008-10-10. Retrieved 2007-04-20.
4. "AUTHORS". GitLab. Retrieved 7 September 2019.
5. ^ "docs · master · cryptsetup / cryptsetup". GitLab. Retrieved 10 October 2024.
6. "The cryptsetup textual domain". Translation Project. Retrieved 7 September 2019.
7. "COPYING". GitLab. Retrieved 7 September 2019.
8. "COPYING.LGPL". GitLab. Retrieved 7 September 2019.
9. "cryptsetup FAQ".
10. Clemens Fruhwirth (2004-07-15). "TKS1 – An anti-forensic, two level, and iterated key setup scheme" (PDF). Draft. Retrieved 2006-12-12.
11. Milan Broz (2012-04-24). "[dm-crypt] Does dm-crypt support journaling filesystem transactional guarantees?". saout.de. Retrieved 2014-07-08.
12. Mikulas Patocka (2009-06-22). "kernel/git/torvalds/linux.git". Linux kernel source tree. kernel.org. Retrieved 2014-07-08.
13. "dm-crypt: Linux kernel device-mapper crypto target – IV generators". cryptsetup. 2014-01-11. Retrieved 2015-04-05.
14. "dm-crypt: Linux kernel device-mapper crypto target". Retrieved 2015-04-05.
15. "[dm-devel] [PATCH 2/2] dm-crypt: Add TCW IV mode for old CBC TCRYPT containers". redhat.com. Retrieved 2014-06-17.
16. Trefny, Vojtech (25 Jan 2020). BitLocker disk encryption on Linux (PDF). DevConf CZ.
17. cryptsetup(8) – Linux Programmer's Manual – Administration and Privileged Commands
18. "Ext2 IFS For Windows". fs-driver.org. Retrieved 15 February 2015.
19. Alex Hornung (2010-07-23). "HEADS UP: dm, lvm, cryptsetup and initrd on master".

External links

• Official dm-crypt, cryptsetup-luks and cryptmount websites
• All about dm-crypt and LUKS on one page (on archive.org) – a page covering dm-crypt/LUKS, starting with theory and ending with many practical examples about its usage.

• Device mapper
• Disk encryption
• Cryptographic software