linux-kernel - [PATCH v4 0/3] LSM: module hierarchy in /proc/.../attr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <599d0a80-0838-2baa-8ee2-7eefafc10cec@schaufler-ca.com>
Date:	Thu, 23 Jun 2016 14:07:20 -0700
From:	Casey Schaufler <casey@...aufler-ca.com>
To:	LSM <linux-security-module@...r.kernel.org>,
	James Morris <jmorris@...ei.org>
Cc:	John Johansen <john.johansen@...onical.com>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Paul Moore <paul@...l-moore.com>,
	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
	Kees Cook <keescook@...omium.org>,
	Casey Schaufler <casey@...aufler-ca.com>,
	LKLM <linux-kernel@...r.kernel.org>
Subject: [PATCH v4 0/3] LSM: module hierarchy in /proc/.../attr

Subject: [PATCH v4 0/3] LSM: module hierarchy in /proc/.../attr

Changes from v3:
	Use kasprintf instead of kzalloc() ... sprintf.

Create interfaces that make it possible to deal with process
attributes in the face of multiple "major" security modules.

Patch 1/3 adds /sys/kernel/security/lsm, which provides
a list of the active security modules on the system.

	$ cat /sys/kernel/security/lsm
	capability,yama,loadpin,smack

Patch 2/3 adds a subdirectory in /proc/.../attr for each
security module that exports process attribute data. This
allows a program in easily differentiate between the "current"
value for Smack and AppArmor.

	$ cat /proc/self/attr/smack/current
	System

	$ cat /proc/self/attr/apparmor/current
	unconfined

Patch 3/3 adds an interface that provides module identified
information that otherwise matches the "current" attr.
This allows a system with multiple modules to provide the
complete security "context" in one place. A (future) system
with both Smack and AppArmor might report:

	$ cat /proc/self/attr/context
	smack='System'apparmor='unconfined'

Signed-off-by: Casey Schaufler <casey@...aufler-ca.com>

---
 Documentation/security/LSM.txt |  26 +++++--
 fs/proc/base.c                 |  95 ++++++++++++++++++++---
 fs/proc/internal.h             |   1 +
 include/linux/lsm_hooks.h      |  12 +--
 include/linux/security.h       |  15 ++--
 security/apparmor/lsm.c        |  37 +++++++--
 security/commoncap.c           |   3 +-
 security/inode.c               |  26 ++++++-
 security/loadpin/loadpin.c     |   2 +-
 security/security.c            | 169 ++++++++++++++++++++++++++++++++++++++++-
 security/selinux/hooks.c       |  24 +++++-
 security/smack/smack_lsm.c     |  23 +++---
 security/tomoyo/tomoyo.c       |   2 +-
 security/yama/yama_lsm.c       |   2 +-
 14 files changed, 382 insertions(+), 55 deletions(-)