[PATCH 04/10] user namespaces: enforce user namespaces for file permission
Eric W. Biederman
ebiederm at xmission.com
Fri Aug 22 19:16:46 PDT 2008
"Serge E. Hallyn" <serue at us.ibm.com> writes:
> That might make sense. I guess the problem is I started trying to
> handle generic permission. But I don't need to... the fs can
> provide its own permission, else we do the simple userns check.
We really need that simple starting place where we can turn it all
on and you aren't allowed to do anything, then we can enable one
feature at a time from there.
Plus I can think of some uses for a user who isn't allowed to do
anything on a machine. ;)
> The user ns comes from the current task. The fs must decide whether
> current->user->uid in current->user->user_ns has capabilities over
> the target file. Only the fs can erify that the user is really
> uid=0 or has CAP_DAC_OVERRIDE, for instance, with respect to the file.
In the general case only the filesystem can make the call about what
powers we have over a specific file and the filesystem will make that
call when we pass it our kerberos ticket to the filesystem server, and
ask the filesystem to perform a specific operation.
In the common case the filesystem is just a reflection of our in memory
set of namespaces. Getting the capability rules straight are going
to be a little interesting. Essentially however for filesystems
I believe the rule is if I have CAP_DAC_OVERRIDE in the user namespace
of a user. And that user creates a namespace. Then I should have
CAP_DAC_OVERRIDE capability over that namespace as well. Allowing
me to back up files in the unprivileged users namespace.
The common case is the only case that needs to be implemented
in generic kernel code.
More information about the Containers