From: James Morris <jmorris@namei.org>
To: Elena Reshetova <elena.reshetova@intel.com>
Cc: kernel-hardening@lists.openwall.com,
linux-security-module@vger.kernel.org, keescook@chromium.org,
spender@grsecurity.net, casey.schaufler@intel.com,
michael.leibowitz@intel.com, william.c.roberts@intel.com
Subject: [kernel-hardening] Re: [RFC] [PATCH 0/5] Hardchroot LSM + additional hooks
Date: Wed, 3 Aug 2016 16:36:23 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1608031635340.19613@namei.org> (raw)
In-Reply-To: <1469777680-3687-1-git-send-email-elena.reshetova@intel.com>
On Fri, 29 Jul 2016, Elena Reshetova wrote:
> fs/fhandle.c | 5 +
> fs/fs_struct.c | 7 +-
> fs/namespace.c | 15 +-
> fs/open.c | 3 +
> include/linux/lsm_hooks.h | 37 ++
> include/linux/security.h | 19 +
> kernel/fork.c | 5 +
> security/Kconfig | 1 +
> security/Makefile | 2 +
> security/hardchroot/Kconfig | 10 +
> security/hardchroot/Makefile | 3 +
> security/hardchroot/hardchroot_lsm.c | 654 +++++++++++++++++++++++++++++++++++
> security/security.c | 30 ++
> 13 files changed, 786 insertions(+), 5 deletions(-)
> create mode 100644 security/hardchroot/Kconfig
> create mode 100644 security/hardchroot/Makefile
> create mode 100644 security/hardchroot/hardchroot_lsm.c
Please cc: Al Viro on these changes.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2016-08-03 6:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 7:34 [kernel-hardening] [RFC] [PATCH 0/5] Hardchroot LSM + additional hooks Elena Reshetova
2016-07-29 7:34 ` [kernel-hardening] [RFC] [PATCH 1/5] path_fchdir and path_fhandle LSM hooks Elena Reshetova
2016-07-29 18:12 ` Jann Horn
2016-07-31 10:55 ` Reshetova, Elena
2016-07-31 12:02 ` Jann Horn
2016-07-31 18:28 ` Reshetova, Elena
2016-07-31 21:23 ` Jann Horn
2016-08-01 8:38 ` Reshetova, Elena
2016-07-29 7:34 ` [kernel-hardening] [RFC] [PATCH 2/5] task_unshare LSM hook Elena Reshetova
2016-07-29 17:58 ` Jann Horn
2016-07-29 18:17 ` Reshetova, Elena
2016-07-29 7:34 ` [kernel-hardening] [RFC] [PATCH 3/5] sb_unsharefs " Elena Reshetova
2016-07-29 18:02 ` Jann Horn
2016-07-29 18:09 ` Reshetova, Elena
2016-07-29 18:15 ` Jann Horn
2016-07-29 18:19 ` Reshetova, Elena
2016-07-29 7:34 ` [kernel-hardening] [RFC] [PATCH 4/5] invoke path_chroot() LSM hook on mntns_install() Elena Reshetova
2016-07-29 18:11 ` Jann Horn
2016-07-31 10:39 ` Reshetova, Elena
2016-07-31 11:29 ` Jann Horn
2016-08-01 9:26 ` Reshetova, Elena
2016-07-29 7:34 ` [kernel-hardening] [RFC] [PATCH 5/5] Hardchroot LSM Elena Reshetova
2016-07-29 11:44 ` [kernel-hardening] " Brad Spengler
2016-07-29 12:15 ` [kernel-hardening] " Reshetova, Elena
2016-07-29 12:25 ` Reshetova, Elena
2016-07-29 18:53 ` [kernel-hardening] " Jann Horn
2016-07-29 19:20 ` Casey Schaufler
2016-07-29 20:53 ` Jann Horn
2016-07-29 21:10 ` Casey Schaufler
2016-07-29 21:50 ` Jann Horn
2016-07-30 6:10 ` Reshetova, Elena
2016-08-03 6:36 ` James Morris [this message]
2016-08-05 7:53 ` [kernel-hardening] RE: [RFC] [PATCH 0/5] Hardchroot LSM + additional hooks Reshetova, Elena
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=alpine.LRH.2.20.1608031635340.19613@namei.org \
--to=jmorris@namei.org \
--cc=casey.schaufler@intel.com \
--cc=elena.reshetova@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-security-module@vger.kernel.org \
--cc=michael.leibowitz@intel.com \
--cc=spender@grsecurity.net \
--cc=william.c.roberts@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.