|author||Manoj Gupta <firstname.lastname@example.org>||Thu Nov 29 13:02:31 2018 -0800|
|committer||chrome-bot <email@example.com>||Sat Dec 01 01:08:36 2018 -0800|
verity: Remove static builds. No need to have static verity builds. BUG=chromium:909983 TEST=verity builds CQ-DEPEND=CL:1355514 Change-Id: Idb19d158c7464c82649ef4eb701216b9d48070c3 Reviewed-on: https://chromium-review.googlesource.com/1355513 Commit-Ready: Manoj Gupta <firstname.lastname@example.org> Tested-by: Manoj Gupta <email@example.com> Reviewed-by: Mike Frysinger <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.