-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more docs #196
Add more docs #196
Conversation
During upstream overlayfs work, the default for verity xattr was changed to verity=off, so there is no need to specifically have a wey to disable it. All that results in is mount error on kernels that don't support verity=. So, we just support ENABLE_VERITY which implies verity=require, which is the thing we want anyway. Signed-off-by: Alexander Larsson <[email protected]>
2d88c14
to
3d493f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Simplifies the mkcomposefs arguments to always compute digest and by-digest payloads, dropping the --absolute option and related things, as we couldn't think of a usecase for it right now. If we have a more precise usecase later we can add it back in a way that makes sense for the usecase. Signed-off-by: Alexander Larsson <[email protected]>
Signed-off-by: Alexander Larsson <[email protected]>
Signed-off-by: Alexander Larsson <[email protected]>
3d493f9
to
ce58c0d
Compare
} | ||
|
||
if (opt_verity) | ||
if (opt_verity || opt_digest != NULL) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is one of the bigger changes here right? I think this makes sense...no point in verifying the digest without also doing underlying verity I guess?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, i think it would be surprising if you successfully mounted against a particular digest, but then you can still read back modified data from the mount.
This adds the simplify commits that was missing from #195, and updates the docs for mkcomposefs and mount.composefs.