Run clang-format on missed files

It turnes out I missed a few files when doing the
merge (crrev.com/c/2363183). Hopefully these are the last of them. No
manual changes. Just clang-format on a copy in platform2/verity and
rsynced back to platform/verity.

BUG=chromium:886953
TEST=CQ passes

Change-Id: Ib28f34bd23f19185770873dca9c5ef0b9549e634
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/dm-verity/+/2363568
Tested-by: Amin Hassani <ahassani@chromium.org>
Auto-Submit: Amin Hassani <ahassani@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Commit-Queue: Amin Hassani <ahassani@chromium.org>
6 files changed
tree: 46c7adf66cfb6ac7d52c024d753e4ba90ec8fd68
  1. .gitignore
  2. LICENSE
  3. LICENSE.makefile
  4. Makefile
  5. OWNERS
  6. PRESUBMIT.cfg
  7. README.md
  8. common.mk
  9. dm-bht-userspace.c
  10. dm-bht-userspace.h
  11. dm-bht.c
  12. dm-bht.h
  13. dm-bht_unittest.cc
  14. file_hasher.cc
  15. file_hasher.h
  16. file_hasher_unittest.cc
  17. include/
  18. kernel/
  19. logging.h
  20. logging/
  21. simple_file/
  22. utils.cc
  23. utils.h
  24. verity_main.cc
  25. verity_testrunner.cc
README.md

Verity

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:

  • [hash of hash of blocks n ... n+n-1]
  • [hash of hash of blocks 0 ... n-1]
  • [...]
  • [hash of block 1]
  • [hash of block 0]

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.

Building

To build outside of Chromium OS:

make

Example Usage

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

Licensing

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.