diff options
author | Christian Göttsche <cgzones@googlemail.com> | 2023-05-11 14:32:12 +0200 |
---|---|---|
committer | Paul Moore <paul@paul-moore.com> | 2023-05-23 15:37:56 -0400 |
commit | 8bfbd046a3a8883c476eab1de6eb526f62bdc9d1 (patch) | |
tree | c3c77e70516ad6850480f89458bed6f05f8c6c5f /security/security.c | |
parent | eb14232fb7713fa6258fa876d6d387c03ec21868 (diff) | |
download | lwn-8bfbd046a3a8883c476eab1de6eb526f62bdc9d1.tar.gz lwn-8bfbd046a3a8883c476eab1de6eb526f62bdc9d1.zip |
selinux: deprecated fs ocon
The object context type `fs`, not to be confused with the well used
object context type `fscon`, was introduced in the initial git commit
1da177e4c3f4 ("Linux-2.6.12-rc2") but never actually used since.
The paper "A Security Policy Configuration for the Security-Enhanced
Linux" [1] mentions it under `7.2 File System Contexts` but also states:
Currently, this configuration is unused.
The policy statement defining such object contexts is `fscon`, e.g.:
fscon 2 3 gen_context(system_u:object_r:conA_t,s0) \
gen_context(system_u:object_r:conB_t,s0)
It is not documented at selinuxproject.org or in the SELinux notebook
and not supported by the Reference Policy buildsystem - the statement is
not properly sorted - and thus not used in the Reference or Fedora
Policy.
Print a warning message at policy load for each such object context:
SELinux: void and deprecated fs ocon 02:03
This topic was initially highlighted by Nicolas Iooss [2].
[1]: https://media.defense.gov/2021/Jul/29/2002815735/-1/-1/0/SELINUX-SECURITY-POLICY-CONFIGURATION-REPORT.PDF
[2]: https://lore.kernel.org/selinux/CAJfZ7=mP2eJaq2BfO3y0VnwUJaY2cS2p=HZMN71z1pKjzaT0Eg@mail.gmail.com/
Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
[PM: tweaked deprecation comment, description line wrapping]
Signed-off-by: Paul Moore <paul@paul-moore.com>
Diffstat (limited to 'security/security.c')
0 files changed, 0 insertions, 0 deletions