I confidently expect them to ride the ‘SELinux is totally fine’ train all the way into the ground. I’m sure they will be shocked and upset when something like OpenBSD’s pledge() is integrated either in Linux libraries or as a kernel security module (or both) and people start switching to it.
While I agree that SELinux is too complex, this misses the point. pledge() helps defending against vulnerabilities in programs that are cooperative. SELinux is quite different in that it also protects against programs that are not cooperative, see e.g. the use of SELinux in app sandboxing in SELinux:
I confidently expect them to ride the ‘SELinux is totally fine’ train all the way into the ground. I’m sure they will be shocked and upset when something like OpenBSD’s pledge() is integrated either in Linux libraries or as a kernel security module (or both) and people start switching to it.
While I agree that SELinux is too complex, this misses the point. pledge() helps defending against vulnerabilities in programs that are cooperative. SELinux is quite different in that it also protects against programs that are not cooperative, see e.g. the use of SELinux in app sandboxing in SELinux:
https://source.android.com/security/selinux/