All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: linux-integrity@vger.kernel.org,
	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,
	Yuqiong Sun <suny@us.ibm.com>,
	Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>,
	John Johansen <john.johansen@canonical.com>
Subject: Re: [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support
Date: Fri, 13 Apr 2018 12:25:02 -0400	[thread overview]
Message-ID: <1523636702.3272.63.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87sh8lcecn.fsf@xmission.com>

[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.

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.

Mimi

WARNING: multiple messages have this Message-ID (diff)
From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support
Date: Fri, 13 Apr 2018 12:25:02 -0400	[thread overview]
Message-ID: <1523636702.3272.63.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87sh8lcecn.fsf@xmission.com>

[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.

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.

Mimi

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: linux-integrity@vger.kernel.org,
	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,
	Yuqiong Sun <suny@us.ibm.com>,
	Mehmet Kayaalp <mkayaalp@linux.vnet.ibm.com>,
	John Johansen <john.johansen@canonical.com>
Subject: Re: [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support
Date: Fri, 13 Apr 2018 12:25:02 -0400	[thread overview]
Message-ID: <1523636702.3272.63.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <87sh8lcecn.fsf@xmission.com>

[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.

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.

Mimi

  parent reply	other threads:[~2018-04-13 16:25 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 13:57 [RFC PATCH v3 0/3] ima: namespacing IMA Stefan Berger
2018-03-27 13:57 ` Stefan Berger
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   ` Stefan Berger
     [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
2018-03-27 13:57     ` Stefan Berger
2018-03-27 13:57     ` Stefan Berger
2018-03-27 23:01     ` Eric W. Biederman
2018-03-27 23:01       ` Eric W. Biederman
     [not found]       ` <87sh8lcecn.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2018-03-28 11:10         ` Stefan Berger
2018-04-13 16:25         ` Mimi Zohar
2018-03-28 11:10       ` Stefan Berger
2018-03-28 11:10         ` Stefan Berger
2018-03-28 12:14         ` Dr. Greg Wettstein
2018-03-28 12:14           ` Dr. Greg Wettstein
2018-03-28 12:44           ` Stefan Berger
2018-03-28 12:44             ` Stefan Berger
     [not found]           ` <20180328121418.GA24712-DHO+NtfOqB5PEDpkEIzg7wC/G2K4zDHf@public.gmane.org>
2018-03-28 12:44             ` Stefan Berger
     [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
2018-04-18 15:59         ` John Johansen
2018-04-18 15:59           ` John Johansen
2018-04-18 15:59           ` John Johansen
2018-04-13 16:25       ` Mimi Zohar [this message]
2018-04-13 16:25         ` Mimi Zohar
2018-04-13 16:25         ` Mimi Zohar
2018-04-18 16:09         ` John Johansen
2018-04-18 16:09           ` John Johansen
2018-04-18 16:09           ` John Johansen
     [not found]           ` <d8c30d7d-c679-9323-7a25-d3148e9b96c6-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2018-04-18 19:57             ` Mimi Zohar
2018-04-18 19:57           ` Mimi Zohar
2018-04-18 19:57             ` Mimi Zohar
2018-04-18 19:57             ` Mimi Zohar
     [not found]             ` <1524081472.3272.319.camel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-18 20:12               ` Eric W. Biederman
2018-04-18 20:12                 ` Eric W. Biederman
2018-04-18 20:12                 ` Eric W. Biederman
2018-04-18 20:12                 ` Eric W. Biederman
     [not found]                 ` <87wox4s282.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2018-04-18 20:27                   ` Mimi Zohar
2018-04-18 20:27                     ` Mimi Zohar
2018-04-18 20:27                     ` Mimi Zohar
2018-04-18 20:27                     ` Mimi Zohar
2018-04-18 21:32                   ` John Johansen
2018-04-18 21:32                 ` John Johansen
2018-04-18 21:32                   ` John Johansen
2018-04-18 21:32                   ` John Johansen
2018-04-19 11:03                   ` Stefan Berger
2018-04-19 11:03                     ` Stefan Berger
2018-04-19 15:35                     ` John Johansen
2018-04-19 15:35                       ` John Johansen
2018-04-19 15:35                       ` John Johansen
     [not found]                       ` <f84ae8af-fa5b-9f31-fbef-5a49f90dd45a-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2018-04-26 21:18                         ` Stefan Berger
2018-04-26 21:18                       ` Stefan Berger
2018-04-26 21:18                         ` Stefan Berger
     [not found]                         ` <0d2b2635-d7fb-d240-7dd0-2a81014c58ba-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-27  0:49                           ` Eric W. Biederman
2018-04-27  0:49                         ` Eric W. Biederman
2018-04-27  0:49                           ` Eric W. Biederman
     [not found]                     ` <2103bbb9-3f2a-78f8-f7ad-28859659973f-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-19 15:35                       ` John Johansen
     [not found]                   ` <8895cb9c-7b9e-2f82-e3d8-a15f5fc26e25-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2018-04-19 11:03                     ` Stefan Berger
     [not found]         ` <1523636702.3272.63.camel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-18 16:09           ` John Johansen
     [not found]     ` <1522159038-14175-2-git-send-email-stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-03-27 23:01       ` 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
2018-03-27 13:57 ` Stefan Berger
2018-03-27 13:57   ` 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
2018-03-29 17:44   ` Dr. Greg Wettstein
2018-03-29 17:44   ` Dr. Greg Wettstein
2018-04-02 11:20   ` Stefan Berger
2018-04-02 11:20     ` Stefan Berger
2018-04-03 15:04     ` Dr. Greg Wettstein
2018-04-03 15:04       ` Dr. Greg Wettstein
     [not found]     ` <d7e1b214-6565-6c0b-9cdc-2b3dec361161-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2018-04-03 15:04       ` Dr. Greg Wettstein
     [not found]   ` <201803291744.w2THiZoV005866-DHO+NtfOqB5PEDpkEIzg7wC/G2K4zDHf@public.gmane.org>
2018-04-02 11:20     ` 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=1523636702.3272.63.camel@linux.vnet.ibm.com \
    --to=zohar@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=john.johansen@canonical.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=mkayaalp@linux.vnet.ibm.com \
    --cc=serge@hallyn.com \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=suny@us.ibm.com \
    --cc=sunyuqiong1988@gmail.com \
    --cc=tycho@docker.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.