Disabling SELinux's runtime disable

Posted Apr 21, 2023 12:30 UTC (Fri) by ceplm (subscriber, #41334)
In reply to: Disabling SELinux's runtime disable by taladar
Parent article: Disabling SELinux's runtime disable

https://www.reddit.com/r/openSUSE/comments/118twi8/why_is...

Not speaking for SUSE, but it seems to me that we are switching from AppArmor to SELinux (at least with ALP and MicroOS, I guess Tumbleweed will follow as well, and the system I write this on is MicroOS with SELinux Enforcing and my office computer is Tumbleweed with SELinux also in the Enforcing mode).

It seems that the last stand of AppArmor is now Debian/Ubuntu. Debian has certainly enough strength to keep it alive, but otherwise there is a long list of Ubuntu-only projects which later died and where replaced by the projects used by the rest of the Linux universe.

to post comments

Disabling SELinux's runtime disable

Posted Apr 21, 2023 14:23 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link]

> Not speaking for SUSE, but it seems to me that we are switching from AppArmor to SELinux (at least with ALP and MicroOS, I guess Tumbleweed will follow as well..

Interesting. Earlier SUSE explicitly noted this:
https://documentation.suse.com/sles/12-SP4/html/SLES-all/...
"Because many organizations are requesting SELinux to be in the Linux distributions they are using, SUSE is offering support for the SELinux framework in SUSE Linux Enterprise Server. This does not mean that the default installation of SUSE Linux Enterprise Server will switch from AppArmor to SELinux in the near future."

I am assuming the situation has evolved since then.