Lines Matching full:hash

21     This is the type of the on-disk hash format.
37     This is the device that supplies the hash tree data.  It may be
44     Each block corresponds to one digest on the hash device.
47     The size of a hash block in bytes.
56     to the root block of the hash tree.
59     The cryptographic hash algorithm used for this device.  This should
63     The hexadecimal encoding of the cryptographic hash of the root hash block
64     and the salt.  This hash should be trusted as there is no other authenticity
96     Use forward error correction (FEC) to recover from corruption if hash
98     may be the same device where data and hash blocks reside, in which case
99     fec_start must be outside data and hash areas.
102     on the hash device after the hash blocks.
104     Note: block sizes for data and hash devices must match. Also, if the
127     Hash blocks are still verified each time they are read from the hash device,
128     since verification of hash blocks is less performance critical than data
129     blocks, and a hash block will not be verified any more after all the data
135     the root hash during the creation of the device mapper block device.
159 tree, the root hash, then the I/O will fail.  This should detect
160 tampering with any data on the device and the hash data.
163 per-block basis. This allows for a lightweight hash computation on first read
168 corrupted data will be verified using the cryptographic hash of the
172 Hash Tree
175 Each node in the tree is a cryptographic hash.  If it is a leaf node, the hash
177 the hash of a number of child nodes is calculated.
204 It only reads the hash blocks which directly follow the header.
212 Directly following the header (and with sector number padded to the next hash
213 block boundary) are the hash blocks which are stored a depth at a time
236 the hash tree or activate the kernel device. This is available from
240 Create hash on the device::
244   Root hash: 4392712ba01368efdf14b05c76f9e4df0d53664630b5d48632ed17a137f39076