On 15/09/2016 01:24, Alexei Starovoitov wrote: > On Thu, Sep 15, 2016 at 01:02:22AM +0200, Mickaël Salaün wrote: >>> >>> I would suggest for the next RFC to do minimal 7 patches up to this point >>> with simple example that demonstrates the use case. >>> I would avoid all unpriv stuff and all of seccomp for the next RFC as well, >>> otherwise I don't think we can realistically make forward progress, since >>> there are too many issues raised in the subsequent patches. >> >> I hope we will find a common agreement about seccomp vs cgroup… I think >> both approaches have their advantages, can be complementary and nicely >> combined. > > I don't mind having both task based lsm and cgroup based as long as > infrastracture is not duplicated and scaling issues from earlier version > are resolved. It should be much better with this RFC. > I'm proposing to do cgroup only for the next RFC, since mine and Sargun's > use case for this bpf+lsm+cgroup is _not_ security or sandboxing. Well, LSM purpose is to do security stuff. The main goal of Landlock is to bring security features to userland, including unprivileged processes, at least via the seccomp interface [1]. > No need for unpriv, no_new_priv to cgroups are other things that Andy > is concerned about. I'm concern about security too! :) > >> Unprivileged sandboxing is the main goal of Landlock. This should not be >> a problem, even for privileged features, thanks to the new subtype/access. > > yes. the point that unpriv stuff can come later after agreement is reached. > If we keep arguing about seccomp details this set won't go anywhere. > Even in basic part (which is cgroup+bpf+lsm) are plenty of questions > to be still agreed. Using the seccomp(2) (unpriv) *interface* is OK according to a more recent thread [1]. [1] https://lkml.kernel.org/r/20160915044852.GA66000@xxxxxxxxxxxxxxxxxxxxxxx > >> Agreed. With this RFC, the Checmate features (i.e. network helpers) >> should be able to sit on top of Landlock. > > I think neither of them should be called fancy names for no technical reason. > We will have only one bpf based lsm. That's it and it doesn't > need an obscure name. Directory name can be security/bpf/..stuff.c I disagree on an LSM named "BPF". I first started with the "seccomp LSM" name (first RFC) but I later realized that it is confusing because seccomp is associated to its syscall and the underlying features. Same thing goes for BPF. It is also artificially hard to grep on a name too used in the kernel source tree. Making an association between the generic eBPF mechanism and a security centric approach (i.e. LSM) seems a bit reductive (for BPF). Moreover, the seccomp interface [1] can still be used. Landlock is a nice name to depict a sandbox as an enclave (i.e. a landlocked country/state). I want to keep this name, which is simple, express the goal of Landlock nicely and is comparable to other sandbox mechanisms as Seatbelt or Pledge. Landlock should not be confused with the underlying eBPF implementation. Landlock could use more than only eBPF in the future and eBPF could be used in other LSM as well. Mickaël
Attachment:
signature.asc
Description: OpenPGP digital signature
