Kees Cook 9d8dad742a Yama: higher restrictions should block PTRACE_TRACEME ... The higher ptrace restriction levels should be blocking even PTRACE_TRACEME requests. The comments in the LSM documentation are misleading about when the checks happen (the parent does not go through security_ptrace_access_check() on a PTRACE_TRACEME call). Signed-off-by: Kees Cook <keescook@chromium.org> Cc: stable@vger.kernel.org # 3.5.x and later Signed-off-by: James Morris <james.l.morris@oracle.com>		2012-08-10 19:58:07 +10:00
..
apparmor
integrity	ima: audit is compiled only when enabled	2012-07-05 16:43:59 -04:00
keys	Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security	2012-07-23 18:49:06 -07:00
selinux	selinux: tag avc cache alloc as non-critical	2012-07-31 18:42:47 -07:00
smack	smack: off by one error	2012-07-30 15:04:17 +10:00
tomoyo
yama	Yama: higher restrictions should block PTRACE_TRACEME	2012-08-10 19:58:07 +10:00
capability.c
commoncap.c
device_cgroup.c
inode.c
Kconfig
lsm_audit.c
Makefile
min_addr.c
security.c	security: Fix nommu build.	2012-07-03 21:41:03 +10:00