veritysetup
manage dm-verity (block level verification) volumes
- Provided by: cryptsetup-bin (Version: 2:1.6.6-5ubuntu2.1)
- Source: cryptsetup
- Report a bug
manage dm-verity (block level verification) volumes
veritysetup <options> <action> <action args>
Veritysetup is used to configure dm-verity managed device-mapper mappings.
Device-mapper verity target provides read-only transparent integrity checking of block devices using kernel crypto API.
The dm-verity devices are always read-only.
Veritysetup supports these operations:
format <data_device> <hash_device>
Note you need to provide root hash string for device verification or activation. Root hash must be trusted.
The data or hash device argument can be block device or file image. If hash device path doesn't exist, it will be created as file.
<options> can be [--hash, --no-superblock, --format, --data-block-size, --hash-block-size, --data-blocks, --hash-offset, --salt, --uuid]
create <name> <data_device> <hash_device> <root_hash>
The <root_hash> is a hexadecimal string.
<options> can be [--hash-offset, --no-superblock]
If option --no-superblock is used, you have to use as the same options as in initial format operation.
verify <data_device> <hash_device> <root_hash>
This command performs userspace verification, no kernel device is created.
The <root_hash> is a hexadecimal string.
<options> can be [--hash-offset, --no-superblock]
If option --no-superblock is used, you have to use as the same options as in initial format operation.
remove <name>
status <name>
dump <hash_device>
<options> can be [--no-superblock]
The UUID must be provided in standard UUID format, e.g. 12345678-1234-1234-1234-123456789abc.
Veritysetup returns 0 on success and a non-zero value on error.
Error codes are: 1 wrong parameters, 2 no permission, 3 out of memory, 4 wrong device specified, 5 device already exists or device is busy.
Report bugs, including ones in the documentation, on the cryptsetup mailing list at <dm-crypt@saout.de> or in the 'Issues' section on LUKS website. Please attach the output of the failed command with the --debug option added.
The first implementation of veritysetup was written by Chrome OS authors.
This version is based on verification code written by Mikulas Patocka <mpatocka@redhat.com> and rewritten for libcryptsetup by Milan Broz <gmazyland@gmail.com>.
Copyright © 2012-2013 Red Hat, Inc.
Copyright © 2012-2014 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 http://code.google.com/p/cryptsetup/
The verity on-disk format specification available at http://code.google.com/p/cryptsetup/wiki/DMVerity