> > What is left unspecified here is 'how' a child 'with its own profile' is
> > confined here. Are it is confined to just its own profile, it may that
> > the "complicit process" communication may need to be wider specified to
> > include this.
Sorry have to bring this up. cgroups why not? Assign application to
a cgroup that contains there filesystem access permissions. Done
right this could even be stacked. Only give less access to
application unless LSM particularly overrides.
Comtainers allow overriding / in chroot style. This needs file or
label based protection no matter the security framework. So we don't
have the chroot problems of applications breaking out.
Apparmors file access control features along with selinux's as a
combined into a cgroup would be good.
Same is required for device control.
There are reasons why I keep on bring containers up it changes the
model. Yes I know coming to a common agreement in these sections will
not be simple. But at some point it has to be done.
-
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]
