From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: linux-integrity@vger.kernel.org
Cc: containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, tycho@docker.com,
serge@hallyn.com, sunyuqiong1988@gmail.com, david.safford@ge.com,
mkayaalp@cs.binghamton.edu,
James.Bottomley@HansenPartnership.com, zohar@linux.vnet.ibm.com,
ebiederm@xmission.com, Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: [RFC PATCH v3 0/3] ima: namespacing IMA
Date: Tue, 27 Mar 2018 09:57:15 -0400 [thread overview]
Message-ID: <1522159038-14175-1-git-send-email-stefanb@linux.vnet.ibm.com> (raw)
This patch set implements an IMA namespace data structure that gets
created alongside a user namespace with CLONE_NEWUSER, and lays down the
foundation for namespacing the different aspects of IMA (eg. IMA-audit,
IMA-measurement, IMA-appraisal).
The original PoC patches [1] created a new CLONE_NEWIMA flag to explicitly
control when a new IMA namespace should be created. The previously posted
version 2 of this series had it hooked on the mount namespace, which was
regarded as inappropriate. Based on comments, we elected to hang the IMA
namepace off of the existing user namespace now. In this patch series we
are adding a pointer to the user_namespace pointing to the ima_namespace.
Both are now tied together and joining the user_namespace with setns() also
joins the ima_namespace that was created along with it.
The first patch creates the ima_namespace data, while the second patch
puts the iint->flags in the namespace. The third patch uses these flags
for namespacing the IMA-audit messages, enabling the same file to be
audited each time it is accessed in a new namespace.
Stefan
Mehmet Kayaalp (2):
ima: Add ns_status for storing namespaced iint data
ima: mamespace audit status flags
Yuqiong Sun (1):
ima: extend clone() with IMA namespace support
include/linux/ima.h | 67 +++++++++
include/linux/user_namespace.h | 4 +
init/Kconfig | 10 ++
kernel/user.c | 7 +
kernel/user_namespace.c | 18 +++
security/integrity/ima/Makefile | 3 +-
security/integrity/ima/ima.h | 47 ++++++-
security/integrity/ima/ima_api.c | 8 +-
security/integrity/ima/ima_init.c | 4 +
security/integrity/ima/ima_init_ima_ns.c | 43 ++++++
security/integrity/ima/ima_main.c | 15 ++-
security/integrity/ima/ima_ns.c | 225 +++++++++++++++++++++++++++++++
12 files changed, 443 insertions(+), 8 deletions(-)
create mode 100644 security/integrity/ima/ima_init_ima_ns.c
create mode 100644 security/integrity/ima/ima_ns.c
--
2.14.3
next reply other threads:[~2018-03-27 13:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 13:57 Stefan Berger [this message]
2018-03-27 13:57 ` [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support Stefan Berger
2018-03-27 23:01 ` Eric W. Biederman
2018-03-28 11:10 ` Stefan Berger
2018-03-28 12:14 ` Dr. Greg Wettstein
2018-03-28 12:44 ` Stefan Berger
2018-04-18 15:59 ` John Johansen
2018-04-13 16:25 ` Mimi Zohar
2018-04-18 16:09 ` John Johansen
2018-04-18 19:57 ` Mimi Zohar
2018-04-18 20:12 ` Eric W. Biederman
2018-04-18 20:27 ` Mimi Zohar
2018-04-18 21:32 ` John Johansen
2018-04-19 11:03 ` Stefan Berger
2018-04-19 15:35 ` John Johansen
2018-04-26 21:18 ` Stefan Berger
2018-04-27 0:49 ` Eric W. Biederman
2018-03-27 13:57 ` [RFC PATCH v3 2/3] ima: Add ns_status for storing namespaced iint data Stefan Berger
2018-03-27 13:57 ` [RFC PATCH v3 3/3] ima: mamespace audit status flags Stefan Berger
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=1522159038-14175-1-git-send-email-stefanb@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=containers@lists.linux-foundation.org \
--cc=david.safford@ge.com \
--cc=ebiederm@xmission.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mkayaalp@cs.binghamton.edu \
--cc=serge@hallyn.com \
--cc=sunyuqiong1988@gmail.com \
--cc=tycho@docker.com \
--cc=zohar@linux.vnet.ibm.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 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®