summaryrefslogtreecommitdiff
path: root/security/safesetid
diff options
context:
space:
mode:
authorThomas Cedeno <thomascedeno@google.com>2020-07-16 22:13:57 +0300
committerMicah Morton <mortonm@chromium.org>2020-10-13 19:17:34 +0300
commit111767c1d86bd9661f8b72ace50cbcb13507a1bf (patch)
treeeb61e1cd69c7b43ce363d8cde1c67ae0751eeb37 /security/safesetid
parentbbf5c979011a099af5dc76498918ed7df445635b (diff)
downloadlinux-111767c1d86bd9661f8b72ace50cbcb13507a1bf.tar.xz
LSM: Signal to SafeSetID when setting group IDs
For SafeSetID to properly gate set*gid() calls, it needs to know whether ns_capable() is being called from within a sys_set*gid() function or is being called from elsewhere in the kernel. This allows SafeSetID to deny CAP_SETGID to restricted groups when they are attempting to use the capability for code paths other than updating GIDs (e.g. setting up userns GID mappings). This is the identical approach to what is currently done for CAP_SETUID. NOTE: We also add signaling to SafeSetID from the setgroups() syscall, as we have future plans to restrict a process' ability to set supplementary groups in addition to what is added in this series for restricting setting of the primary group. Signed-off-by: Thomas Cedeno <thomascedeno@google.com> Signed-off-by: Micah Morton <mortonm@chromium.org>
Diffstat (limited to 'security/safesetid')
0 files changed, 0 insertions, 0 deletions