integritysetup - manage dm-integrity (block level integrity) volumes
integritysetup <options> <action> <action args>
Integritysetup is used to configure dm-integrity managed device-mapper mappings.
Device-mapper integrity target provides read-write transparent integrity checking of block devices. The dm-integrity target emulates additional data integrity field per-sector. You can use this additional field directly with integritysetup utility, or indirectly (for authenticated encryption) through cryptsetup.
Integritysetup supports these operations:
Formats <device> (calculates space and dm-integrity superblock and wipes the device).
<options> can be [−−data−device, −−batch−mode, −−no−wipe, −−journal−size, −−interleave−sectors, −−tag−size, −−integrity, −−integrity−key−size, −−integrity−key−file, −−sector−size, −−progress-frequency]
create <name> <device> (OBSOLETE syntax)
Open a mapping with <name> backed by device <device>.
<options> can be [−−data−device, −−batch−mode, −−journal−watermark, −−journal−commit−time, −−buffer−sectors, −−integrity, −−integrity−key−size, −−integrity−key−file, −−integrity−no−journal, −−integrity−recalculate, −−integrity−recalculate-reset,−−integrity−recovery−mode, −−allow−discards]
Removes existing mapping <name>.
For backward compatibility, there is remove command alias for the close command.
<options> can be [−−deferred] or [−−cancel−deferred]
Reports status for the active integrity mapping <name>.
Reports parameters from on-disk stored superblock.
Print more information on command execution.
Run in debug mode with full diagnostic logs. Debug output lines are always prefixed by ’#’.
Show the program version.
Do not ask for confirmation.
Print separate line every <seconds> with wipe progress.
Do not wipe the device after format. A device that is not initially wiped will contain invalid checksums.
−−journal−size, −j BYTES
Size of the journal.
The number of interleaved sectors.
Automatically recalculate integrity tags in kernel on activation. The device can be used during automatic integrity recalculation but becomes fully integrity protected only after the background operation is finished. This option is available since the Linux kernel version 4.19.
Restart recalculation from the beginning of the device. It can be used to change the integrity checksum function. Note it does not change the tag length. This option is available since the Linux kernel version 5.13.
Journal watermark in percents. When the size of the journal exceeds this watermark, the journal flush will be started.
Commit time in milliseconds. When this time passes (and no explicit flush operation was issued), the journal is written.
−−tag−size, −t BYTES
Size of the integrity tag per-sector (here the integrity function will store authentication tag).
NOTE: The size can be smaller that output size of the hash function, in that case only part of the hash will be stored.
Specify a separate data device that contains existing data. The <device> then will contain calculated integrity tags and journal for this data device.
−−sector−size, −s BYTES
Sector size (power of two: 512, 1024, 2048, 4096).
The number of sectors in one buffer.
The tag area is accessed using buffers, the large buffer size means that the I/O size will be larger, but there could be less I/Os issued.
−−integrity, −I ALGORITHM
Use internal integrity calculation (standalone mode). The integrity algorithm can be CRC (crc32c/crc32) or hash function (sha1, sha256).
For HMAC (hmac-sha256) you have also to specify an integrity key and its size.
The size of the data integrity key. Maximum is 4096 bytes.
The file with the integrity key.
Disable journal for integrity device.
Use alternate bitmap mode (available since Linux kernel 5.2) where dm-integrity uses bitmap instead of a journal. If a bit in the bitmap is 1, the corresponding region’s data and integrity tags are not synchronized - if the machine crashes, the unsynchronized regions will be recalculated. The bitmap mode is faster than the journal mode, because we don’t have to write the data twice, but it is also less reliable, because if data corruption happens when the machine crashes, it may not be detected.
Number of 512-byte sectors per bitmap bit, the value must be power of two.
Bitmap flush time in milliseconds.
In case of a crash, it is possible that the data and integrity tag doesn’t match if the journal is disabled.
Recovery mode (no journal, no tag checking).
NOTE: The following options are intended for testing purposes only.
Using journal encryption does not make sense without encryption the data, these options are internally used in authenticated disk encryption with cryptsetup(8).
Integrity algorithm for journal area. See −−integrity option for detailed specification.
The size of the journal integrity key. Maximum is 4096 bytes.
The file with the integrity key.
Encryption algorithm for journal data area. You can use a block cipher here such as cbc-aes or a stream cipher, for example, chacha20 or ctr-aes.
The size of the journal encryption key. Maximum is 4096 bytes.
The file with the journal encryption key.
Allow the use of discard (TRIM) requests for the device. This option is available since the Linux kernel version 5.7.
Defers device removal in close command until the last user closes it.
Removes a previously configured deferred device removal in close command.
The dm-integrity target is available since Linux kernel version 4.12.
Format and activation of an integrity device always require superuser privilege because the superblock is calculated and handled in dm-integrity kernel target.
Do not use these options until you need compatibility with specific old kernel.
Use inefficient legacy padding.
Use old flawed HMAC calclation (also does not protect superblock).
Allow insecure recalculating of volumes with HMAC keys (recalcualtion offset in superblock is not protected).
Integritysetup returns 0 on success and a non-zero value on error.
1 wrong parameters
2 no permission
3 out of memory
4 wrong device specified
5 device already exists, or device is busy.
Format the device with default standalone mode (CRC32C):
integritysetup format <device>
Open the device with default parameters:
integritysetup open <device> test
Format the device in standalone mode for use with HMAC(SHA256):
integritysetup format <device> −−tag−size 32 −−integrity hmac−sha256 −−integrity−key−file <keyfile> −−integrity−key−size <key_bytes>
Open (activate) the device with HMAC(SHA256) and HMAC key in file:
integritysetup open <device> test −−integrity hmac−sha256 −−integrity−key−file <keyfile> −−integrity−key−size <key_bytes>
Dump dm-integrity superblock information:
integritysetup dump <device>
Report bugs, including ones in the documentation, on the cryptsetup mailing list at <firstname.lastname@example.org> or in the ’Issues’ section on LUKS website. Please attach the output of the failed command with the −−debug option added.
The integritysetup tool is written by Milan Broz <email@example.com> and is part of the cryptsetup project.
© 2016-2021 Red Hat, Inc.
Copyright © 2016-2021 Milan Broz
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
The project website at https://gitlab.com/cryptsetup/cryptsetup
The integrity on-disk format specification available at https://gitlab.com/cryptsetup/cryptsetup/wikis/DMIntegrity