From: Casey Schaufler <casey@schaufler-ca.com>
To: LSM <linux-security-module@vger.kernel.org>,
James Morris <jmorris@namei.org>
Cc: John Johansen <john.johansen@canonical.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Paul Moore <paul@paul-moore.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Kees Cook <keescook@chromium.org>,
Casey Schaufler <casey@schaufler-ca.com>,
LKLM <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/3] LSM: module hierarchy in /proc/.../attr
Date: Fri, 10 Jun 2016 14:21:59 -0700 [thread overview]
Message-ID: <e4357a80-22ba-1531-014b-43f2d6a085e1@schaufler-ca.com> (raw)
Subject: [PATCH v3 0/3] LSM: module hierarchy in /proc/.../attr
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@schaufler-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 | 167 ++++++++++++++++++++++++++++++++++++++++-
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, 380 insertions(+), 55 deletions(-)
next reply other threads:[~2016-06-10 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 21:21 Casey Schaufler [this message]
2016-06-10 21:25 ` [PATCH v3 1/3] LSM: Add /sys/kernel/security/lsm Casey Schaufler
2016-06-14 18:41 ` Kees Cook
2016-06-14 19:32 ` Casey Schaufler
2016-06-14 22:25 ` David A. Wheeler
2016-06-10 21:25 ` [PATCH v3 2/3] LSM: module hierarchy in /proc/.../attr Casey Schaufler
2016-06-14 18:43 ` Kees Cook
2016-06-14 19:27 ` Casey Schaufler
2016-06-14 21:24 ` Kees Cook
2016-06-10 21:25 ` [PATCH v3 3/3] LSM: Add context interface for proc attr Casey Schaufler
2016-06-14 18:57 ` Kees Cook
2016-06-14 20:19 ` Casey Schaufler
2016-06-14 21:07 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4357a80-22ba-1531-014b-43f2d6a085e1@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®