|author||Jorge Lucangeli Obes <firstname.lastname@example.org>||Tue Jun 18 13:10:32 2019 -0400|
|committer||Chris McDonald <email@example.com>||Wed Jun 19 02:42:02 2019 +0000|
verity: Update OWNERS file. We'd like to have at least two active owners on each project. Start by adding Mattias and we can later transition this to other members of the security team. BUG=None TEST=None Change-Id: I5979c8271a39e2a23363c6166cdd2ac1849a3c48 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/dm-verity/+/1663998 Reviewed-by: Chris McDonald <firstname.lastname@example.org> Reviewed-by: Mattias Nissler <email@example.com> Legacy-Commit-Queue: Commit Bot <firstname.lastname@example.org> Commit-Queue: Jorge Lucangeli Obes <email@example.com> Tested-by: Chris McDonald <firstname.lastname@example.org>
Verity is the userspace tool for creating integrity hashes for a device image.
This tool is a frontend for dm-bht, a device-mapper friendly block hash table structure. `verity' produces dm-bht-based images for use with dm-verity. The dm-verity module provides a transparent, integrity-checking layer over a given block device. This expects a backing device and a secondary device which provides cryptographic digests of the blocks on the primary device
Note, the secondary device image can be appended to the primary device or used as a standalone device.
This tool creates an image of the format:
Upon completion, the hash of the root hash will be printed to standard out. The root hash, tree depth, number of hashed blocks, and cryptographic hash algorithm used must be supplied to the dm-verity when configuring a device.
To build outside of Chromium OS:
./verity mode depth alg image hash_image [root_hexdigest]
dd if=/dev/zero of=/tmp/image bs=4k count=512 ./verity create 2 sha256 /tmp/image /tmp/hash | tee table # ... cat table ls -la /tmp/hash
All the source code is licensed GPLv2 to be completely kernel compatible. The Makefiles are from the parent project and are licensed under a BSD-style license.