lkml.org 
[lkml]   [2008]   [Dec]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH 2/2] user namespaces: require cap_set{ug}id for CLONE_NEWUSER
"Serge E. Hallyn" <serue@us.ibm.com> writes:

>> Personally the user namespace only becomes interesting when we
>> start to be able to move in the other direction and remove the
>> set of capabilities requires to create it.
>>
>> Eric
>
> Agreed. Now the thing is I don't think we need full userns
> support to get there. We just need the targeted capabilities
> and the basic dummy fs support - that is, init_user_ns owns
> all vfsmounts, and anyone not in init_user_ns only gets
> user other access to files under those mounts.

Right.

> Of course complete support for targeted caps will in itself
> be a huge effort :)
>
> So my roadmap is: next address the per-user keyring, then
> the targeted caps.

Sounds good.

I expect this means we will pass through a period where the user
namespace is less useful than it is today. But as it will be on
a much firmer foundation that is fine.

Eric



\
 
 \ /
  Last update: 2008-12-05 18:29    [W:0.068 / U:0.220 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site