Skip to content

SELinux: Validate kernel object classes and permissions

Chad Sellers selinux 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4SELinux: remove current object class and permission validation mechanismsecurity/selinux/ss/services.c+0 -910 replies
2/4SELinux: export object class and permission definitionssecurity/selinux/avc.c security/selinux/include/avc_ss.h+35 -121 reply
3/4SELinux: ensure keys constant in hashtab_searchsecurity/selinux/ss/hashtab.c security/selinux/ss/hashtab.h security/selinux/ss/symtab.c+12 -120 replies
4/4SELinux: validate kernel object classes and permissionssecurity/selinux/ss/services.c+158 -14 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/4] SELinux: Validate kernel object classes and permissions

This replaces the object class and permission validation code in the SELinux security server. The current code validates that the object classes and permissions have not changed between policy loads. This requires a simple reboot to circumvent, and more importantly does not allow for any change in object classes or permissions upon reload (say if a new userspace object manager was added to the system).

The new logic simply verifies the values of object classes and permissions against the kernel headers in security/selinux/include. If a class or permission in the new policy that is defined in the kernel headers does not match the kernel headers, then policy will fail to load. Note that there is no longer any comparison between the old policy and the new policy.

--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.