From: Mimi Zohar <zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: John Johansen
<john.johansen-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
Mehmet Kayaalp
<mkayaalp-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
sunyuqiong1988-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
david.safford-JJi787mZWgc@public.gmane.org,
James Bottomley
<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>,
linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mkayaalp-4hyTIkVWTs8LubxHQvXPfYdd74u8MsAO@public.gmane.org,
linux-integrity-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support
Date: Wed, 18 Apr 2018 16:27:08 -0400 [thread overview]
Message-ID: <1524083228.3272.331.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87wox4s282.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
On Wed, 2018-04-18 at 15:12 -0500, Eric W. Biederman wrote:
> Mimi Zohar <zohar@linux.vnet.ibm.com> writes:
>
> > On Wed, 2018-04-18 at 09:09 -0700, John Johansen wrote:
> >> On 04/13/2018 09:25 AM, Mimi Zohar wrote:
> >> > [Cc'ing John Johansen]
> >> >
> >> > On Tue, 2018-03-27 at 18:01 -0500, Eric W. Biederman wrote:
> >> > [...]
> >> >> As such I expect the best way to create the ima namespace is by simply
> >> >> writing to securityfs/imafs. Possibly before the user namespace is
> >> >> even unshared. That would allow IMA to keep track of things from
> >> >> before a container is created.
> >> >
> >>
> >> I do think this is generally the right approach for LSMs when looking
> >> forward to LSM stacking and more LSMs.
> >>
> >>
> >> > My initial thought was to stage IMA namespacing with just IMA-audit
> >> > first, followed by either IMA-measurement or IMA-appraisal. This
> >> > would allow us to get the basic IMA namespacing framework working and
> >> > defer dealing with the securityfs related namespacing of the IMA
> >> > policy and measurement list issues to later.
> >> >
> >> > By tying IMA namespacing to a securityfs ima/unshare file, we would
> >> > need to address the securityfs issues first.
> >> >
> >>
> >> well it depends on what you want to do. It would be possible to have
> >> a simple file (not a jump link) within securityfs that IMA could use
> >> without having to deal with all the securityfs issues first. However it
> >> does require that securityfs (not necessarily imafs) be visible within
> >> the mount namespace of the task doing the setup.
> >
> > Eric, would you be OK with that?
>
> Roughly. My understanding is that you have to have a write to some
> filesystem to set the ima policy.
>
> I was expecting having to write an "create ima namespace" value
> to the filesystem would not be any special effort.
>
> Now it sounds like providing the "create an ima namespace" is going to
> be a special case, and that does not sound correct.
This is not any different than any of the other security/ima/ files
(eg. policy, ascii_runtime_measurements, ...). The next IMA
namespacing stage would add support for these files.
Mimi
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2018-04-18 20:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1522159038-14175-1-git-send-email-stefanb@linux.vnet.ibm.com>
[not found] ` <1522159038-14175-1-git-send-email-stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-03-27 13:57 ` [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support Stefan Berger
[not found] ` <1522159038-14175-2-git-send-email-stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-03-27 23:01 ` Eric W. Biederman
[not found] ` <87sh8lcecn.fsf@xmission.com>
[not found] ` <bc03161e-394b-bf4d-48c4-858dcf05458a@linux.vnet.ibm.com>
[not found] ` <bc03161e-394b-bf4d-48c4-858dcf05458a-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-03-28 12:14 ` Dr. Greg Wettstein
2018-04-18 15:59 ` John Johansen
[not found] ` <20180328121418.GA24712@wind.enjellic.com>
[not found] ` <20180328121418.GA24712-DHO+NtfOqB5PEDpkEIzg7wC/G2K4zDHf@public.gmane.org>
2018-03-28 12:44 ` Stefan Berger
[not found] ` <87sh8lcecn.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2018-03-28 11:10 ` Stefan Berger
2018-04-13 16:25 ` Mimi Zohar
[not found] ` <1523636702.3272.63.camel@linux.vnet.ibm.com>
[not found] ` <1523636702.3272.63.camel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-18 16:09 ` John Johansen
[not found] ` <d8c30d7d-c679-9323-7a25-d3148e9b96c6@canonical.com>
[not found] ` <d8c30d7d-c679-9323-7a25-d3148e9b96c6-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2018-04-18 19:57 ` Mimi Zohar
[not found] ` <1524081472.3272.319.camel@linux.vnet.ibm.com>
[not found] ` <1524081472.3272.319.camel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-18 20:12 ` Eric W. Biederman
[not found] ` <87wox4s282.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2018-04-18 20:27 ` Mimi Zohar [this message]
2018-04-18 21:32 ` John Johansen
[not found] ` <8895cb9c-7b9e-2f82-e3d8-a15f5fc26e25@canonical.com>
[not found] ` <8895cb9c-7b9e-2f82-e3d8-a15f5fc26e25-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2018-04-19 11:03 ` Stefan Berger
[not found] ` <2103bbb9-3f2a-78f8-f7ad-28859659973f@linux.vnet.ibm.com>
[not found] ` <2103bbb9-3f2a-78f8-f7ad-28859659973f-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-19 15:35 ` John Johansen
[not found] ` <f84ae8af-fa5b-9f31-fbef-5a49f90dd45a@canonical.com>
[not found] ` <f84ae8af-fa5b-9f31-fbef-5a49f90dd45a-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2018-04-26 21:18 ` Stefan Berger
[not found] ` <0d2b2635-d7fb-d240-7dd0-2a81014c58ba@linux.vnet.ibm.com>
[not found] ` <0d2b2635-d7fb-d240-7dd0-2a81014c58ba-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
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
[not found] <stefanb@linux.vnet.ibm.com>
2018-03-29 17:44 ` [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support Dr. Greg Wettstein
[not found] ` <201803291744.w2THiZoV005866-DHO+NtfOqB5PEDpkEIzg7wC/G2K4zDHf@public.gmane.org>
2018-04-02 11:20 ` Stefan Berger
[not found] ` <d7e1b214-6565-6c0b-9cdc-2b3dec361161@linux.vnet.ibm.com>
[not found] ` <d7e1b214-6565-6c0b-9cdc-2b3dec361161-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-03 15:04 ` Dr. Greg Wettstein
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=1524083228.3272.331.camel@linux.vnet.ibm.com \
--to=zohar-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=david.safford-JJi787mZWgc@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=john.johansen-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=linux-integrity-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mkayaalp-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=mkayaalp-4hyTIkVWTs8LubxHQvXPfYdd74u8MsAO@public.gmane.org \
--cc=sunyuqiong1988-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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