Hi!
> > Can we enhance private namespaces so they can squash setuid/setgid? If so,
> > is that adequate?
>
> We could. But that would again be overly restrictive. The goal is to
> make the use of FUSE filesystems for users as simple as possible. If
> the user has to manage multiple namespaces, each with it's own
> restrictions, it's becoming a very un-user-friendly environment.
Actually I think this solution is way less ugly. We have precent: if
task is ptraced, suid bits on anything it execs are ignored.
I don't think user interface issues belong to the kernel (and I do not
think different namespaces are that bad for the user; various chroots
and ld_preload hacks already work that way)
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
-
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]
