linux.git/security/yama, branch v5.2-rc2

treewide: Add SPDX license identifier - Makefile/Kconfig

2019-05-21T08:50:46+00:00

Add SPDX license identifiers to all Make/Kconfig files which:

 - Have no license information of any form

These files fall under the project license, GPL v2 only. The resulting SPDX
license identifier is:

  GPL-2.0-only

Signed-off-by: Thomas Gleixner 
Signed-off-by: Greg Kroah-Hartman

Yama: mark local symbols as static

2019-03-28T17:02:29+00:00

sparse complains that Yama defines functions and a variable as non-static
even though they don't exist in any header. Fix it by making them static.

Co-developed-by: Mukesh Ojha 
Signed-off-by: Mukesh Ojha 
Signed-off-by: Jann Horn 
[kees: merged similar static-ness fixes into a single patch]
Link: https://lkml.kernel.org/r/20190326230841.87834-1-jannh@google.com
Link: https://lkml.kernel.org/r/1553673018-19234-1-git-send-email-mojha@codeaurora.org
Signed-off-by: Kees Cook 
Signed-off-by: James Morris

Merge tag 'v5.0-rc3' into next-general

2019-01-22T22:33:10+00:00

Sync to Linux 5.0-rc3 to pull in the VFS changes which impacted a lot
of the LSM code.

Yama: Check for pid death before checking ancestry

2019-01-16T20:00:56+00:00

It's possible that a pid has died before we take the rcu lock, in which
case we can't walk the ancestry list as it may be detached. Instead, check
for death first before doing the walk.

Reported-by: syzbot+a9ac39bf55329e206219@syzkaller.appspotmail.com
Fixes: 2d514487faf1 ("security: Yama LSM")
Cc: stable@vger.kernel.org
Suggested-by: Oleg Nesterov 
Signed-off-by: Kees Cook 
Signed-off-by: James Morris

Yama: Initialize as ordered LSM

2019-01-08T21:18:43+00:00

This converts Yama from being a direct "minor" LSM into an ordered LSM.

Signed-off-by: Kees Cook 
Reviewed-by: Casey Schaufler

pids: introduce find_get_task_by_vpid() helper

2018-02-07T02:32:46+00:00

There are several functions that do find_task_by_vpid() followed by
get_task_struct().  We can use a helper function instead.

Link: http://lkml.kernel.org/r/1509602027-11337-1-git-send-email-rppt@linux.vnet.ibm.com
Signed-off-by: Mike Rapoport 
Acked-by: Oleg Nesterov 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

doc: ReSTify Yama.txt

2017-05-18T16:33:04+00:00

Adjusts for ReST markup and moves under LSM admin guide.

Signed-off-by: Kees Cook 
Signed-off-by: Jonathan Corbet

security: mark LSM hooks as __ro_after_init

2017-03-06T00:00:15+00:00

Mark all of the registration hooks as __ro_after_init (via the
__lsm_ro_after_init macro).

Signed-off-by: James Morris 
Acked-by:  Stephen Smalley 
Acked-by: Kees Cook

LSM: Add /sys/kernel/security/lsm

2017-01-19T02:18:29+00:00

I am still tired of having to find indirect ways to determine
what security modules are active on a system. I have added
/sys/kernel/security/lsm, which contains a comma separated
list of the active security modules. No more groping around
in /proc/filesystems or other clever hacks.

Unchanged from previous versions except for being updated
to the latest security next branch.

Signed-off-by: Casey Schaufler 
Acked-by: John Johansen 
Acked-by: Paul Moore 
Acked-by: Kees Cook 
Signed-off-by: James Morris

Yama: allow access for the current ptrace parent

2016-12-05T00:48:01+00:00

Under ptrace_scope=1, it's possible to have a tracee that is already
ptrace-attached, but is no longer a direct descendant.  For instance, a
forking daemon will be re-parented to init, losing its ancestry to the
tracer that launched it.

The tracer can continue using ptrace in that state, but it will be
denied other accesses that check PTRACE_MODE_ATTACH, like process_vm_rw
and various procfs files.  There's no reason to prevent such access for
a tracer that already has ptrace control anyway.

This patch adds a case to ptracer_exception_found to allow access for
any task in the same thread group as the current ptrace parent.

Signed-off-by: Josh Stone 
Cc: Kees Cook 
Cc: James Morris 
Cc: "Serge E. Hallyn" 
Cc: linux-security-module@vger.kernel.org
Signed-off-by: Kees Cook 
Signed-off-by: James Morris