Skip to content

Adjusted selinux policy to be more resilient to updates (3.21)#5923

Merged
craigcomstock merged 1 commit into
cfengine:3.21.xfrom
craigcomstock:ENT-13016-selinux-3.21
Oct 29, 2025
Merged

Adjusted selinux policy to be more resilient to updates (3.21)#5923
craigcomstock merged 1 commit into
cfengine:3.21.xfrom
craigcomstock:ENT-13016-selinux-3.21

Conversation

@craigcomstock

Copy link
Copy Markdown
Contributor

In rhel-10 the current policy errored out due to missing key_socket class.
Because we were specifying each class explicitly we were prone to trouble when changes happened in the kernel and selinux-policy (the package/repo which builds the .pp policy file).
Replacing all of the class elements with a single all_kernel_class_perms macro will allow us to get what we want: all of the classes available for use in our policy but in a way that will change outside of our policy.

Ticket: ENT-13016
Changelog: none
(cherry picked from commit 721bbe2)

In rhel-10 the current policy errored out due to missing key_socket class.
Because we were specifying each class explicitly we were prone to trouble when changes happened in the kernel and selinux-policy (the package/repo which builds the .pp policy file).
Replacing all of the class elements with a single all_kernel_class_perms macro will allow us to get what we want: all of the classes available for use in our policy but in a way that will change outside of our policy.

Ticket: ENT-13016
Changelog: none
(cherry picked from commit 721bbe2)
@craigcomstock craigcomstock changed the title Adjusted selinux policy to be more resilient to updates Adjusted selinux policy to be more resilient to updates (3.21) Oct 29, 2025
@craigcomstock craigcomstock merged commit 5eed140 into cfengine:3.21.x Oct 29, 2025
11 checks passed
@craigcomstock craigcomstock deleted the ENT-13016-selinux-3.21 branch October 29, 2025 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants