| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Exactly like for veritysetup/cryptsetup
|
|
|
|
|
| |
Let's make the tool work more like veritysetup/cryptsetup in this regard
too.
|
|
|
|
| |
To make the tool behave more like cryptsetup/veritysetup
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
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.
|