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

..

00-INDEX

security: Yama LSM

2012-02-10 09:18:52 +11:00

apparmor.txt

Create Documentation/security/,

2011-05-19 15:59:38 -07:00

credentials.txt

Documentation: clarify the purpose of LSMs

2011-11-16 12:37:27 +11:00

keys-ecryptfs.txt

encrypted-keys: move ecryptfs documentation to proper location

2011-06-30 19:08:14 +10:00

keys-request-key.txt

Create Documentation/security/,

2011-05-19 15:59:38 -07:00

keys-trusted-encrypted.txt

Documentation: Fix multiple typo in Documentation

2012-03-07 16:08:24 +01:00

keys.txt

KEYS: Add invalidation support

2012-05-11 10:56:56 +01:00

LSM.txt

Documentation: clarify the purpose of LSMs

2011-11-16 12:37:27 +11:00

SELinux.txt

Create Documentation/security/,

2011-05-19 15:59:38 -07:00

Smack.txt

Smack: allow for significantly longer Smack labels v4

2012-05-14 22:48:38 -07:00

tomoyo.txt

Create Documentation/security/,

2011-05-19 15:59:38 -07:00

Yama.txt

Yama: higher restrictions should block PTRACE_TRACEME

2012-08-10 19:58:07 +10:00