Michael Kerrisk <[email protected]> writes:
>
> And again: is CLONE_NEWUSER (to be)implemented for unshare()?
They all should be. Only the pid namespace (not yet merged) looks
like a problem for unshare.
> Thanks Eric. I'm still not so clear though. What is a user name space
> intended to be, and how is it to be used?
>
> Also, when will the implementation be complete? If not by the 2.6.23 final
> release, it seems unfortunate to expose this flag to userspace, since
> further down the road, it will be difficult for userspace to tell whether
> the kernel below it really supports the flag or not. Or am I missing
> something?
Currently the code depends on CONFIG_USER_NS it is CONFIG_EXPERIMENTAL
and defaulting to N.
So no one should be shipping a production with it enabled, hopefully
that is enough, to avoid problems. I think the current implementation
is usable for some small subset of usable.
The basic idea is so that you have different mappings between uid and
gid values (i.e. /etc/passwd stuff) and struct user in the kernel.
Allowing the kernel to know two users with the same uid are distinct.
When you combined all of the namespaces (and when the are finished)
you have what is effective a chroot jail that looks like it has
the kernel all to itself despite other programs running.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
