From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" Subject: Re: [PATCH v2] xattr: Enable security.capability in user namespaces Date: Tue, 25 Jul 2017 22:00:07 -0500 Message-ID: <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> <1500060374.3583.57.camel@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1500060374.3583.57.camel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Mimi Zohar Cc: Theodore Ts'o , Mimi Zohar , containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org, linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Eric W. Biederman" , casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org, lkp-JC7UmRfGjtg@public.gmane.org List-Id: containers.vger.kernel.org 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? From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751856AbdGZDAH (ORCPT ); Tue, 25 Jul 2017 23:00:07 -0400 Received: from h2.hallyn.com ([78.46.35.8]:47202 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751472AbdGZDAB (ORCPT ); Tue, 25 Jul 2017 23:00:01 -0400 Date: Tue, 25 Jul 2017 22:00:07 -0500 From: "Serge E. Hallyn" To: Mimi Zohar Cc: "Eric W. Biederman" , "Serge E. Hallyn" , Stefan Berger , Mimi Zohar , "Theodore Ts'o" , 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 Subject: Re: [PATCH v2] xattr: Enable security.capability in user namespaces Message-ID: <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> <1500060374.3583.57.camel@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1500060374.3583.57.camel@linux.vnet.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? From mboxrd@z Thu Jan 1 00:00:00 1970 From: serge@hallyn.com (Serge E. Hallyn) Date: Tue, 25 Jul 2017 22:00:07 -0500 Subject: [PATCH v2] xattr: Enable security.capability in user namespaces In-Reply-To: <1500060374.3583.57.camel@linux.vnet.ibm.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> <1500060374.3583.57.camel@linux.vnet.ibm.com> Message-ID: <20170726030007.GA10087@mail.hallyn.com> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org 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 at uid=1000 (if 1000 is the kuid of the container's root user) is in fact useful to IMA? -- 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