commit | e4d233306d0a67b2527fbaff03a9d912922a56cd | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@chromium.org> | Mon Sep 17 21:17:11 2018 -0400 |
committer | chrome-bot <chrome-bot@chromium.org> | Wed Sep 19 08:59:31 2018 -0700 |
tree | bcd8da7891a996c389aad5712915b59f6049b0c5 | |
parent | 3619f6218f73967552885d78b8c9f17741059486 [diff] |
update README to be markdown compliant BUG=chromium:878440 TEST=read it Change-Id: I7b61f2a363393aa24f60f0e8a3a125af193c9c90 Reviewed-on: https://chromium-review.googlesource.com/1229245 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@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.