summaryrefslogtreecommitdiffstats
path: root/src/integritysetup (follow)
Commit message (Collapse)AuthorAgeFilesLines
* integritysetup: do not use crypt_init_data_device after crypt_initLuca Boccassi2022-08-041-6/+6
| | | | | | | | crypt_init_data_device() replaces the crypt_device struct with a new allocation, losing the old one, which we get from crypt_init(). Use crypt_set_data_device() instead. Enhance the test to cover this option too.
* integritysetup: also validate volume nameLennart Poettering2022-03-311-0/+6
| | | | Exactly like for veritysetup/cryptsetup
* integritysetup: also port to mangle_none()Lennart Poettering2022-03-311-2/+2
| | | | | Let's make the tool work more like veritysetup/cryptsetup in this regard too.
* integritysetup: log when attempted to detach already detached volumeLennart Poettering2022-03-311-1/+3
| | | | To make the tool behave more like cryptsetup/veritysetup
* integritysetup: rename action → verb, to match other codeLennart Poettering2022-03-311-5/+5
|
* tree-wide: unify some code that looks for --help in the command lineLennart Poettering2022-03-311-5/+3
|
* integritysetup: Check args to prevent assertTony Asleson2021-10-281-7/+11
| | | | | | | The utility function parse_integrity_options is used to both validate integritytab options or validate and return values. In the case where we are validating only and we have specific value options we will assert.
* Add stand-alone dm-integrity supportTony Asleson2021-10-154-0/+463
This adds support for dm integrity targets and an associated /etc/integritytab file which is required as the dm integrity device super block doesn't include all of the required metadata to bring up the device correctly. See integritytab man page for details.