Alright then. I need to read more about this, maybe I was misinformed. But I’m not super convinced yet, maybe you are misinformed (no accusation here, just saying it could be).
Some of the hook points currently supported by LSM include:
* File open, creation, deletion, and movement;
* Filesystem mounting;
* Operations on tasks and processes;
* Operations on sockets (creating, binding sockets, sending and receiving messages, etc.);
The rules around eBPF are more for preventing a process from locking up a kernel thread than what it can access
It was originally created for high speed routing where making decisions about where network traffic goes was too slow in userspace, but they didn’t want a completely custom kernel module
Comments
Alright then. I need to read more about this, maybe I was misinformed. But I’m not super convinced yet, maybe you are misinformed (no accusation here, just saying it could be).
I don’t know your level of programming knowledge, but I will back up the previous poster.
With eBPF you can add code that runs right before various kernel functions, in kernel space (what they’re calling super root)
E.g. https://eunomia.dev/tutorials/19-lsm-connect/
The rules around eBPF are more for preventing a process from locking up a kernel thread than what it can access
It was originally created for high speed routing where making decisions about where network traffic goes was too slow in userspace, but they didn’t want a completely custom kernel module
Sign in to comment. Sign in