Jann Horn 7ef6b3062f LSM: SafeSetID: fix check for setresuid(new1, new2, new3) ... With the old code, when a process with the (real,effective,saved) UID set (1,1,1) calls setresuid(2,3,4), safesetid_task_fix_setuid() only checks whether the transition 1->2 is permitted; the transitions 1->3 and 1->4 are not checked. Fix this. This is also a good opportunity to refactor safesetid_task_fix_setuid() to be less verbose - having one branch per set*uid() syscall is unnecessary. Note that this slightly changes semantics: The UID transition check for UIDs that were not in the old cred struct is now always performed against the policy of the RUID. I think that's more consistent anyway, since the RUID is also the one that decides whether any policy is enforced at all. Signed-off-by: Jann Horn <jannh@google.com> Signed-off-by: Micah Morton <mortonm@chromium.org>		2019-07-15 08:05:37 -07:00
..
Kconfig	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00
lsm.c	LSM: SafeSetID: fix check for setresuid(new1, new2, new3)	2019-07-15 08:05:37 -07:00
lsm.h	LSM: add SafeSetID module that gates setid calls	2019-01-25 11:22:45 -08:00
Makefile	LSM: add SafeSetID module that gates setid calls	2019-01-25 11:22:45 -08:00
securityfs.c	LSM: fix return value check in safesetid_init_securityfs()	2019-02-12 10:59:22 -08:00