linux/security
John Johansen ade3ddc01e AppArmor: Fix dropping of allowed operations that are force audited
The audit permission flag, that specifies an audit message should be
provided when an operation is allowed, was being ignored in some cases.

This is because the auto audit mode (which determines the audit mode from
system flags) was incorrectly assigned the same value as audit mode. The
shared value would result in messages that should be audited going through
a second evaluation as to whether they should be audited based on the
auto audit, resulting in some messages being dropped.

Signed-off-by: John Johansen <john.johansen@canonical.com>
Acked-by: Kees Cook <kees@ubuntu.com>
2012-02-27 11:38:21 -08:00
..
apparmor AppArmor: Fix dropping of allowed operations that are force audited 2012-02-27 11:38:21 -08:00
integrity IMA: fix audit res field to indicate 1 for success and 0 for failure 2012-02-16 12:01:42 +11:00
keys Merge branch 'next-queue' into next 2012-02-09 17:02:34 +11:00
selinux security: trim security.h 2012-02-14 10:45:42 +11:00
smack security: trim security.h 2012-02-14 10:45:42 +11:00
tomoyo TOMOYO: Accept \000 as a valid character. 2012-01-18 10:40:59 +11:00
yama Yama: add PR_SET_PTRACER_ANY 2012-02-16 10:25:18 +11:00
capability.c security: create task_free security callback 2012-02-10 09:14:51 +11:00
commoncap.c security: trim security.h 2012-02-14 10:45:42 +11:00
device_cgroup.c
inode.c securityfs: fix object creation races 2012-01-10 10:20:35 -05:00
Kconfig security: Yama LSM 2012-02-10 09:18:52 +11:00
lsm_audit.c audit: no leading space in audit_log_d_path prefix 2012-01-17 16:17:04 -05:00
Makefile security: Yama LSM 2012-02-10 09:18:52 +11:00
min_addr.c
security.c security: trim security.h 2012-02-14 10:45:42 +11:00