Skip to content
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.

Sign up for GitHub

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

Jump to bottom

postprocess: Automatically propagate user.ostreemeta xattrs in commit #3657

Closed
wants to merge 2 commits into from
Closed

postprocess: Automatically propagate user.ostreemeta xattrs in commit #3657

wants to merge 2 commits into from

Commits on May 5, 2022

  1. core: Add constants for IMA 

    Prep for further work.
    @cgwalters
    cgwalters committed May 5, 2022
    Configuration menu
    Copy the full SHA
    a88e5e2 View commit details
    Browse the repository at this point in the history

  2. 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.ima`
value, but store them inside a `bare-user` repo in the `user.ostreemeta`
xattr.
    @cgwalters
    cgwalters committed May 5, 2022
    Configuration menu
    Copy the full SHA
    e307e38 View commit details
    Browse the repository at this point in the history