diff options
author | Stephen Smalley <sds@tycho.nsa.gov> | 2016-11-18 10:23:09 -0500 |
---|---|---|
committer | Paul Moore <paul@paul-moore.com> | 2016-11-21 15:37:24 -0500 |
commit | 3322d0d64f4e942862a152f6f11137a1f5eac2e9 (patch) | |
tree | c86bdc1084436be2cb25afe9f382764c091db6ee /usr | |
parent | ea49d10eee5a220b717dbf2ee429c9e3d59c978c (diff) |
selinux: keep SELinux in sync with new capability definitions
When a new capability is defined, SELinux needs to be updated.
Trigger a build error if a new capability is defined without
corresponding update to security/selinux/include/classmap.h's
COMMON_CAP2_PERMS. This is similar to BUILD_BUG_ON() guards
in the SELinux nlmsgtab code to ensure that SELinux tracks
new netlink message types as needed.
Note that there is already a similar build guard in
security/selinux/hooks.c to detect when more than 64
capabilities are defined, since that will require adding
a third capability class to SELinux.
A nicer way to do this would be to extend scripts/selinux/genheaders
or a similar tool to auto-generate the necessary definitions and code
for SELinux capability checking from include/uapi/linux/capability.h.
AppArmor does something similar in its Makefile, although it only
needs to generate a single table of names. That is left as future
work.
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
[PM: reformat the description to keep checkpatch.pl happy]
Signed-off-by: Paul Moore <paul@paul-moore.com>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions