postprocess: Automatically propagate user.ostreemeta xattrs in commit #3657
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prep for further work.
This is actually what we should have been doing from the start for all metadata actually. It is a key to ultimately fully operating as non-root. This is specifically prep for having the importer pull IMA signatures from RPM headers, translate them into the standard `security.ima` value, but store them inside a `bare-user` repo in the `user.ostreemeta` xattr.
|
OK I figured out the bug, rolling the fix into #3610 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
core: Add constants for IMA
Prep for further work.
postprocess: Automatically propagate user.ostreemeta xattrs in commit
This is actually what we should have been doing from the start
for all metadata actually. It is a key to ultimately fully operating
as non-root.
This is specifically prep for having the importer pull IMA signatures
from RPM headers, translate them into the standard
security.imavalue, but store them inside a
bare-userrepo in theuser.ostreemetaxattr.