Subject: Re: [PATCH v2] xattr: Enable security.capability in user namespaces
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
        Stefan Berger <stefanb@linux.vnet.ibm.com>,
        Mimi Zohar <zohar@us.ibm.com>, "Theodore Ts'o" <tytso@mit.edu>,
        containers@lists.linux-foundation.org, lkp@01.org,
        linux-kernel@vger.kernel.org, tycho@docker.com,
        James.Bottomley@HansenPartnership.com, vgoyal@redhat.com,
        christian.brauner@mailbox.org, amir73il@gmail.com,
        linux-security-module@vger.kernel.org, casey@schaufler-ca.com
Date: Wed, 26 Jul 2017 09:57:50 -0400
In-Reply-To: <20170726030007.GA10087@mail.hallyn.com>
References: <847ccb2a-30c0-a94c-df6f-091c8901eaa0@linux.vnet.ibm.com>
         <87bmoo8bxb.fsf@xmission.com>
         <9a3010e5-ca2b-5e7a-656b-fcc14f7bec4e@linux.vnet.ibm.com>
         <87h8yf7szd.fsf@xmission.com>
         <65dbe654-0d99-03fa-c838-5a726b462826@linux.vnet.ibm.com>
         <20170714133437.GA16737@mail.hallyn.com>
         <596f808b-e21d-8296-5fef-23c1ce7ab778@linux.vnet.ibm.com>
         <20170714173556.GA19669@mail.hallyn.com>
         <xagsmtp2.20170714182525.6604@vmsdvm4.vnet.ibm.com>
         <1500060374.3583.57.camel@linux.vnet.ibm.com>
         <20170726030007.GA10087@mail.hallyn.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <1501077470.28419.8.camel@linux.vnet.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1082
Lines: 24

On Tue, 2017-07-25 at 22:00 -0500, Serge E. Hallyn wrote:
> On Fri, Jul 14, 2017 at 03:26:14PM -0400, Mimi Zohar wrote:
> > On Fri, 2017-07-14 at 13:17 -0500, Eric W. Biederman wrote:
> > > Which brings us to the semantic question of would it be nice to have
> > > stacked IMA/EVM on the same file.
> > > 
> > > I really don't think we do.  I think allowing multiple keys for
> > > different part of trusting files is easy enough that we should have no
> > > need to fight over which keys do which.
> > 
> > We definitely want to support different policies on the native and in
> > the namespace with different keys and keyrings.
> 
> Ok, so Stefan's code to support userspace in a container reading
> security.ima and getting back the value for security.ima@uid=1000
> (if 1000 is the kuid of the container's root user) is in fact
> useful to IMA?

Definitely!  Root within the namespace needs to be able to read and
write security.ima in order to (re)sign files, with a specific key
known to that container.  Stefan's code provides different views of
the security xattrs.

Mimi