commit | b69aeca51481055c58780981d9e8aa1aef90491b | [log] [tgz] |
---|---|---|
author | Allen Webb <allenwebb@google.com> | Tue Apr 09 23:45:40 2019 |
committer | chrome-bot <chrome-bot@chromium.org> | Fri Apr 19 02:51:49 2019 |
tree | c366bd711ea4d178a6437e3ef091ade3d6a9ccfc | |
parent | 240acaa806e64238b0fda54b478209b6aec430b3 [diff] |
Makefile: Replace calls to gtest-config and gmock-config. These helper utils are no longer available. BUG=chromium:940320 TEST=PreCQ passes Change-Id: Iebff68523e2331b29f0c4b6157c59c13e6c77395 Reviewed-on: https://chromium-review.googlesource.com/1560325 Commit-Ready: Allen Webb <allenwebb@google.com> Tested-by: Allen Webb <allenwebb@google.com> Reviewed-by: Mike Frysinger <vapier@chromium.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:
make
To use:
./verity mode depth alg image hash_image [root_hexdigest]
For example:
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.