From: Casey Schaufler <casey.schaufler@intel.com>
To: kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov,
casey.schaufler@intel.com, dave.hansen@intel.com,
deneen.t.dock@intel.com, kristen@linux.intel.com,
arjan@linux.intel.com
Subject: [PATCH v5 0/5] LSM: Support ptrace sidechannel access checks
Date: Wed, 26 Sep 2018 13:34:41 -0700 [thread overview]
Message-ID: <20180926203446.2004-1-casey.schaufler@intel.com> (raw)
v5: Revamped to match Jiri Kosina <jkosina@suse.cz>
Harden spectrev2 userspace-userspace protection v7
Fixed locking issues in the LSM code.
Dropped the new LSM hook and use a ptrace hook instead.
v4: select namespace checks if user namespaces are enabled
and credential checks are request.
v3: get_task_cred wasn't a good choice due to refcounts.
Use lower level protection instead
v2: SELinux access policy corrected.
Use real_cred instead of cred.
This patchset provide a mechanism by which a security module
can advise the system about potential side-channel vulnerabilities.
The existing security modules have been updated to avoid locking
issues in the face of PTRACE_MODE_SCHED. A new security
module is provided to make determinations regarding task attributes
including namespaces.
Signed-off-by: Casey Schaufler <casey.schaufler@intel.com>
---
include/linux/lsm_hooks.h | 5 +++
kernel/ptrace.c | 2 -
security/Kconfig | 1 +
security/Makefile | 2 +
security/apparmor/domain.c | 2 +-
security/apparmor/include/ipc.h | 2 +-
security/apparmor/ipc.c | 8 ++--
security/apparmor/lsm.c | 5 ++-
security/commoncap.c | 2 +
security/security.c | 1 +
security/selinux/hooks.c | 2 +
security/sidechannel/Kconfig | 13 ++++++
security/sidechannel/Makefile | 1 +
security/sidechannel/sidechannel.c | 88 ++++++++++++++++++++++++++++++++++++++
security/smack/smack_lsm.c | 3 +-
15 files changed, 127 insertions(+), 10 deletions(-)
next reply other threads:[~2018-09-26 20:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 20:34 Casey Schaufler [this message]
2018-09-26 20:34 ` [PATCH v5 1/5] AppArmor: Prepare for PTRACE_MODE_SCHED Casey Schaufler
2018-09-26 21:16 ` Jann Horn
2018-09-26 21:18 ` Jann Horn
2018-09-26 22:47 ` Schaufler, Casey
2018-09-26 20:34 ` [PATCH v5 2/5] Smack: " Casey Schaufler
2018-09-26 21:30 ` Jann Horn
2018-09-26 22:53 ` Schaufler, Casey
2018-09-26 22:58 ` Jann Horn
2018-10-04 7:47 ` Jiri Kosina
2018-10-04 11:36 ` Jann Horn
2018-10-16 11:44 ` Jiri Kosina
2018-09-26 20:34 ` [PATCH v5 3/5] SELinux: " Casey Schaufler
2018-09-27 15:50 ` Stephen Smalley
2018-09-27 16:23 ` Schaufler, Casey
2018-09-26 20:34 ` [PATCH v5 4/5] Capability: Complete PTRACE_MODE_SCHED Casey Schaufler
2018-09-26 21:26 ` Jann Horn
2018-09-26 22:24 ` Schaufler, Casey
2018-09-26 20:34 ` [PATCH v5 5/5] sidechannel: Linux Security Module for sidechannel Casey Schaufler
2018-09-27 21:45 ` James Morris
2018-09-27 22:39 ` Casey Schaufler
2018-09-27 22:47 ` James Morris
2018-09-27 23:19 ` Schaufler, Casey
2018-09-27 23:43 ` James Morris
2018-09-27 23:47 ` Jann Horn
2018-09-28 16:33 ` James Morris
2018-09-28 17:40 ` Schaufler, Casey
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=20180926203446.2004-1-casey.schaufler@intel.com \
--to=casey.schaufler@intel.com \
--cc=arjan@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=deneen.t.dock@intel.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@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;
as well as URLs for NNTP newsgroup(s).