Lines Matching refs:of

4 Device-Mapper's "verity" target provides transparent integrity checking of
17     This is the type of the on-disk hash format.
21       the rest of the block is padded with zeros.
25       padded with zeros to the power of two.
28     This is the device containing data, the integrity of which needs to be
43     The size of a hash block in bytes.
46     The number of data blocks on the data device.  Additional blocks are
51     This is the offset, in <hash_block_size>-blocks, from the start of hash_dev
52     to the root block of the hash tree.
56     be the name of the algorithm, like "sha1".
59     The hexadecimal encoding of the cryptographic hash of the root hash block
64     The hexadecimal encoding of the salt value.
67     Number of optional parameters. If there are no optional parameters,
69     Otherwise #opt_params is the number of following arguments.
71     Example of optional parameters section:
82 Theory of operation
85 dm-verity is meant to be set up as part of a verified boot path.  This
92 disk access.  If they cannot be verified up to the root node of the
96 Cryptographic hashes are used to assert the integrity of the device on a
105 of some data block on disk is calculated. If it is an intermediary node,
106 the hash of a number of child nodes is calculated.
108 Each entry in the tree is a collection of neighboring nodes that fit in one
109 block.  The number is determined based on block_size and the size of the
132 It is expected that a user-space tool will verify the integrity of the
136 be passed via the kernel command-line in a rooted chain of trust where
141 (starting from the root), sorted in order of increasing index.
143 The full specification of kernel parameters and on-disk metadata format