3 Commits

Author	SHA1	Message	Date
Gaël PORTAY	e502940be2	man: update root-hash-signature option with value ... This documents two possible values expected by the option root-hash-signature for veritytab and veritysetup-generator.	2022-03-30 23:45:26 +02:00
Tony Asleson	9a2a6ec4e3	dm-verity: Remove usage of integrity ... There is a difference between dm-verity and dm-integrity. Remove usage of integrity from verity documentation in man pages and target files.	2021-10-14 12:17:02 -05:00
Gaël PORTAY	08b04ec7e7	veritysetup-generator: add support for veritytab ... This adds the support for veritytab. The veritytab file contains at most five fields, the first four are mandatory, the last one is optional: - The first field contains the name of the resulting verity volume; its block device is set up /dev/mapper/</filename>. - The second field contains a path to the underlying block data device, or a specification of a block device via UUID= followed by the UUID. - The third field contains a path to the underlying block hash device, or a specification of a block device via UUID= followed by the UUID. - The fourth field is the roothash in hexadecimal. - The fifth field, if present, is a comma-delimited list of options. The following options are recognized only: ignore-corruption, restart-on-corruption, panic-on-corruption, ignore-zero-blocks, check-at-most-once and root-hash-signature. The others options will be implemented later. Also, this adds support for the new kernel verity command line boolean option "veritytab" which enables the read for veritytab, and the new environment variable SYSTEMD_VERITYTAB which sets the path to the file veritytab to read.	2021-01-15 11:06:11 -05:00