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.

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

Set file contexts for all of /var/lib/pulp #69

Merged
merged 1 commit into from
Aug 21, 2023

Conversation

ekohl
Copy link
Contributor

@ekohl ekohl commented Aug 10, 2023

This wasn't done in the past to coexist with pulp-selinux (from Pulp 2), but those days are long gone. This also makes it easy to set the correct label on /var/lib/pulp/exports (as Katello does).

I think this addresses https://bugzilla.redhat.com/show_bug.cgi?id=2172833

This wasn't done in the past to coexist with pulp-selinux (from Pulp 2),
but those days are long gone. This also makes it easy to set the correct
label on /var/lib/pulp/exports (as Katello does).
@evgeni
Copy link
Member

evgeni commented Aug 11, 2023

@dralley
Copy link

dralley commented Aug 21, 2023

This might also address #65 ?

@mikedep333 mikedep333 merged commit d52394e into pulp:main Aug 21, 2023
3 checks passed
@ekohl ekohl deleted the own-all-of-var-lib-pulp branch August 21, 2023 20:49
@ekohl
Copy link
Contributor Author

ekohl commented Aug 21, 2023

@dralley I'm not sure. Executing code in /var/lib is uncommon so I'd say the common approach would be to create a specific file context for /var/lib/scripts(/.*)? (like pulpcore_user_script_t) and allow execution of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants