3 ms·
> find it annoying when kernel APIs like ublk require io_uring Good. That's a forcing function for making io_uring work in your environment. > bypasses seccom
by quotemstr 2y ago
> find it annoying when kernel APIs like ublk require io_uring
Good. That's a forcing function for making io_uring work in your environment.
> bypasses seccomp
Seccomp sucks.
We shouldn't be enforcing security by filtering system calls, the set of which will grow forever, but instead by describing access control rules on objects, e.g. with SELinux. If your security policy is that your sandbox should be able to read from some file but not write to it, you should do that with real MAC, which applies to all operations , il_uring included. You shouldn't just filter read(2) and write(2) in particular.
We shouldn't hold back evolution in systems interfaces because some people are stuck on bad ways of doing things and won't move.
- accelbred 2y agoSince when can you use a MAC as an unprivileged user on an arbitrary distro?
- burch45 2y agoParent is referring to https://en.m.wikipedia.org/wiki/Mandatory_access_control https://en.m.wikipedia.org/wiki/Mandatory_access_control As opposed to https://en.m.wikipedia.org/wiki/Medium_access_control https://en.m.wikipedia.org/wiki/Medium_access_control
- deleted 2y ago[deleted]
- fulafel 2y agoNot necessarily, how do I use SELinux as a unprivileged user on eg Debian?
- immibis 2y agoseccomp is a mitigation. Once you have already been exploited, if further escalation is prevented by seccomp, or ASLR, or NX stack, or ....... then you got lucky.
- fulafel 2y agoSELinux is a dx/ux hostile nightmare that we definitely shouldn't be springing on everybody.