Difference between revisions of "Dm-crypt"

From ArchWiki
Jump to: navigation, search
m (grammar)
(simplification and beautification of wikilinks (interactive))
(Tag: wiki-scripts)
 
(3 intermediate revisions by 2 users not shown)
Line 16: Line 16:
 
{{Related articles end}}
 
{{Related articles end}}
  
From the cryptsetup project's [https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt wiki]:
+
dm-crypt is the Linux kernel's [[Wikipedia:device mapper|device mapper]] crypto target. From [[Wikipedia:dm-crypt]], it is a:
 
+
:a transparent disk encryption subsystem in [the] Linux kernel.... [It 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.
:Device-mapper is infrastructure in the Linux 2.6 and 3.x kernel that provides a generic way to create virtual layers of block devices. Device-mapper crypt target provides transparent encryption of block devices using the kernel crypto API. The user can basically specify one of the symmetric ciphers, an encryption mode, a key (of any allowed size), an iv generation mode and then the user can create a new block device in /dev. Writes to this device will be encrypted and reads decrypted. You can mount your filesystem on it as usual or stack dm-crypt device with another device like RAID or LVM volume. Basic documentation of dm-crypt mapping table comes with kernel source and the latest version is available in git repository.
 
  
 
== Common scenarios ==
 
== Common scenarios ==
  
This part introduces common scenarios to employ ''dm-crypt'' to encrypt a system or individual filesystem mount points. It is meant as a starting point to getfamiliarized with different practical encryption procedures. The scenarios cross-link to the other subpages where needed.   
+
This part introduces common scenarios to employ ''dm-crypt'' to encrypt a system or individual filesystem mount points. It is meant as a starting point to get familiarized with different practical encryption procedures. The scenarios cross-link to the other subpages where needed.   
  
 
See [[dm-crypt/Encrypting a non-root file system]] if you need to encrypt a device that is not used for booting a system, like a [[dm-crypt/Encrypting a non-root file system#Partition|partition]] or a [[dm-crypt/Encrypting a non-root file system#Loop device|loop device]].
 
See [[dm-crypt/Encrypting a non-root file system]] if you need to encrypt a device that is not used for booting a system, like a [[dm-crypt/Encrypting a non-root file system#Partition|partition]] or a [[dm-crypt/Encrypting a non-root file system#Loop device|loop device]].
Line 34: Line 33:
 
== Device encryption ==
 
== Device encryption ==
  
[[dm-crypt/Device encryption]] covers how to manually utilize dm-crypt to encrypt a system through the [[dm-crypt/Device encryption#Cryptsetup usage|cryptsetup]] command. It covers examples of the [[dm-crypt/Device encryption#Encryption options with dm-crypt|Encryption options with dm-crypt]], deals with the creation of [[dm-crypt/Device encryption#Keyfiles|keyfiles]], LUKS specific commands for [[dm-crypt/Device encryption#Key management|key management]] as well as for  [[dm-crypt/Device encryption#Backup and restore|Backup and restore]].  
+
[[dm-crypt/Device encryption]] covers how to manually utilize dm-crypt to encrypt a system through the [[cryptsetup]] command. It covers examples of the [[dm-crypt/Device encryption#Encryption options with dm-crypt|Encryption options with dm-crypt]], deals with the creation of [[dm-crypt/Device encryption#Keyfiles|keyfiles]], LUKS specific commands for [[dm-crypt/Device encryption#Key management|key management]] as well as for  [[dm-crypt/Device encryption#Backup and restore|Backup and restore]].  
  
 
== System configuration ==
 
== System configuration ==

Latest revision as of 09:22, 2 August 2018

dm-crypt is the Linux kernel's device mapper crypto target. From Wikipedia:dm-crypt, it is a:

a transparent disk encryption subsystem in [the] Linux kernel.... [It 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.

Common scenarios

This part introduces common scenarios to employ dm-crypt to encrypt a system or individual filesystem mount points. It is meant as a starting point to get familiarized with different practical encryption procedures. The scenarios cross-link to the other subpages where needed.

See dm-crypt/Encrypting a non-root file system if you need to encrypt a device that is not used for booting a system, like a partition or a loop device.

See dm-crypt/Encrypting an entire system if you want to encrypt an entire system, in particular a root partition. Several scenarios are covered, including the use of dm-crypt with the LUKS extension, plain mode encryption and encryption and LVM.

Drive preparation

dm-crypt/Drive preparation deals with operations like securely erasing the drive and dm-crypt specific points for partitioning it.

Device encryption

dm-crypt/Device encryption covers how to manually utilize dm-crypt to encrypt a system through the cryptsetup command. It covers examples of the Encryption options with dm-crypt, deals with the creation of keyfiles, LUKS specific commands for key management as well as for Backup and restore.

System configuration

dm-crypt/System configuration illustrates how to configure mkinitcpio, the boot loader and the crypttab file when encrypting a system.

Swap device encryption

dm-crypt/Swap encryption covers how to add a swap partition to an encrypted system, if required. The swap partition must be encrypted as well to protect any data swapped out by the system. This part details methods without and with suspend-to-disk support.

Specialties

dm-crypt/Specialties deals with special operations like securing the unencrypted boot partition, using GPG or OpenSSL encrypted keyfiles, a method to boot and unlock via the network, another for setting up discard/TRIM for a SSD, and sections dealing with the encrypt hook and multiple disks.

See also