On Thu, Aug 22, 2019 at 04:17:43PM +0200, Daniel Borkmann wrote: > > > > Hence unprivileged bpf is actually something that can be deprecated. > > There is actually a publicly known use-case on unprivileged bpf wrt > socket filters, see the SO_ATTACH_BPF on sockets section as an example: > > https://blog.cloudflare.com/cloudflare-architecture-and-how-bpf-eats-the-world/ > > If I'd have to take a good guess, I'd think it's major use-case is in > SO_ATTACH_REUSEPORT_EBPF in the wild, I don't think the sysctl can be > outright flipped or deprecated w/o breaking existing applications unless > it's cleanly modeled into some sort of customizable CAP_BPF* type policy > (more below) where this would be the lowest common denominator. The cloudflare use case is the perfect example that a lot of program types are used together. Do people use SO_ATTACH_BPF ? Of course. All program types are used by somebody. Before accepting them we had long conversations with authors to understand that the use cases are real. Some progs are probably used less than others by now. Like cls_bpf without exts_integrated is probably not used at all. We still have to support it, of course. That cloudflare example demonstrates that kernel.unprivileged_bpf_disabled=1 is a reality. Companies that care about security already switched it on. Different bits in cloudflare setup need different level of capabilities. Some (like SO_ATTACH_BPF) need unpriv. Another need CAP_NET_ADMIN. But common demoninator for them all is still CAP_SYS_ADMIN. And that's why the system as a whole is not as safe as it could have been with CAP_BPF. The system needs root in many places. Folks going out of the way to reduce that SYS_ADMIN to something less. The example with systemd and NET_ADMIN is just one of them.
