Stemming from a security researcher and his team proposing a new Linux Security Module (LSM) three years ago and it not being accepted to the mainline kernel, he raised issue over the lack of review/action to Linus Torvalds and the mailing lists. In particular, seeking more guidance for how new LSMs should be introduced and raised the possibility of taking the issue to the Linux Foundation Technical Advisory Board (TAB).
This mailing list post today laid out that a proposed TSEM LSM for a framework for generic security modeling was proposed but saw little review activity in the past three years or specific guidance on getting that LSM accepted to the Linux kernel. Thus seeking documented guidance on new Linux Security Module submissions for how they should be optimally introduced otherwise the developers are “prepared to pursue this through the [Technical Advisory Board] if necessary.”
A list of Linux Security Modules is at https://en.wikipedia.org/wiki/Linux_Security_Modules
List of Linux Security Modules
snark
(I didn’t read the wiki page closely. Why was the heading “Adoption” and not something more clear?)
AppArmor Integrity Policy Enforcement (IPE)[6] Landlock[7][8] LoadPin[9] SafeSetID[10] SELinux Smack TOMOYO Yama[11]As a long time SysAdmin, but not your SysAdmin, I have used two of these. Both had terrible documentation for which many “must use” paid software vendors advise disabling the Security Module as a first step.
If random software vendors’ lowest paid intern cannot figure out the settings for arbitrary Linux Security Modules, then the first line of the directions will always be to disable the security module. This leads to them not being used in many cases where the security module would be helpful.
snark
(To explain, it is only the cheapest and most inexperienced person that is typically responsible for doing things as they are not in meetings all day.)
I agree with Linus.