From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tycho Andersen via Containers Subject: Re: [PATCH v4] Introduce v3 namespaced file capabilities Date: Tue, 13 Jun 2017 11:14:22 -0600 Message-ID: <20170613171422.i5vsylhqqo736car__20623.025406576$1497374078$gmane$org@smitten> References: <20170507092105.GA67584@inn.lkp.intel.com> <20170508044408.GA11400@mail.hallyn.com> <20170508181156.GA23112@mail.hallyn.com> <9f80188c-df03-066a-5dac-785cc711d064@linux.vnet.ibm.com> Reply-To: Tycho Andersen Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <9f80188c-df03-066a-5dac-785cc711d064-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: Stefan Berger Cc: Mimi Zohar , containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, LKML , xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, "Eric W. Biederman" , lkp-JC7UmRfGjtg@public.gmane.org List-Id: containers.vger.kernel.org Hi Stefan, On Tue, Jun 13, 2017 at 11:47:26AM -0400, Stefan Berger wrote: > On 05/08/2017 02:11 PM, Serge E. Hallyn wrote: > > Root in a non-initial user ns cannot be trusted to write a traditional > > security.capability xattr. If it were allowed to do so, then any > > unprivileged user on the host could map his own uid to root in a private > > namespace, write the xattr, and execute the file with privilege on the > > host. > > > > However supporting file capabilities in a user namespace is very > > desirable. Not doing so means that any programs designed to run with > > limited privilege must continue to support other methods of gaining and > > dropping privilege. For instance a program installer must detect > > whether file capabilities can be assigned, and assign them if so but set > > setuid-root otherwise. The program in turn must know how to drop > > partial capabilities, and do so only if setuid-root. > > Hi Serge, > > > I have been looking at patch below primarily to learn how we could apply a > similar technique to security.ima and security.evm for a namespaced IMA. > From the paragraphs above I thought that you solved the problem of a shared > filesystem where one now can write different security.capability xattrs by > effectively supporting for example security.capability[uid=1000] and > security.capability[uid=2000] written into the filesystem. Each would then > become visible as security.capability if the userns mapping is set > appropriately. One disadvantage of this approach is that whoever is setting up the container would need to go touch the security.ima attribute for each file in the contianer, which would slow down container creation time. For capabilities this makes sense, because you might want the file to have different capabilities in different namespaces, but for IMA, since the file hash will be the same in every namespace, it would be nice to use a design that avoids touching each file on new ns creation. Cheers, Tycho