From: Richard Haines <richard_c_haines@btinternet.com>
To: selinux@vger.kernel.org
Cc: paul@paul-moore.com, Richard Haines <richard_c_haines@btinternet.com>
Subject: [PATCH V2 3/7] object_classes_permissions.md: Deprecate lockdown class
Date: Wed, 8 Dec 2021 12:16:50 +0000 [thread overview]
Message-ID: <20211208121654.7591-4-richard_c_haines@btinternet.com> (raw)
In-Reply-To: <20211208121654.7591-1-richard_c_haines@btinternet.com>
Add text regarding the removal of lockdown hooks from kernel 5.16.
Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
---
src/object_classes_permissions.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/object_classes_permissions.md b/src/object_classes_permissions.md
index b092a9b..4ad8520 100644
--- a/src/object_classes_permissions.md
+++ b/src/object_classes_permissions.md
@@ -70,7 +70,7 @@
- [Performance Event Object Class](#performance-event-object-class)
- [*perf_event*](#perf_event)
- [Lockdown Object Class](#lockdown-object-class)
- - [*lockdown*](#lockdown)
+ - [*lockdown* (Deprecated)](#lockdown-deprecated)
- [IPC Object Classes](#ipc-object-classes)
- [*ipc* (Deprecated)](#ipc-deprecated)
- [*sem*](#sem)
@@ -1674,15 +1674,15 @@ Control ***perf**(1)* events
## Lockdown Object Class
-Note: If the *lockdown* LSM is enabled alongside SELinux, then the
-lockdown access control will take precedence over the SELinux lockdown
-implementation.
+The *lockdown* class and associated SELinux LSM hook (added in kernel 5.6),
+have been removed from kernel 5.16 for the reasons discussed in
+<https://lore.kernel.org/selinux/163292547664.17566.8479687865641275719.stgit@olly/>.
-### *lockdown*
+### *lockdown* (Deprecated)
Stop userspace extracting/modify kernel data.
-**Permissions** - 6 unique permissions:
+**Permissions** - 2 unique permissions:
*confidentiality*
--
2.33.1
next prev parent reply other threads:[~2021-12-08 12:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 12:16 [PATCH V2 0/7] Various SELinux Notebook updates Richard Haines
2021-12-08 12:16 ` [PATCH V2 1/7] notebook: Minor formatting fixes Richard Haines
2021-12-08 20:05 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 2/7] object_classes_permissions.md: Correct the context object class entry Richard Haines
2021-12-08 20:09 ` Paul Moore
2021-12-08 12:16 ` Richard Haines [this message]
2021-12-08 20:10 ` [PATCH V2 3/7] object_classes_permissions.md: Deprecate lockdown class Paul Moore
2021-12-08 12:16 ` [PATCH V2 4/7] policy_config_files.md: Update openrc_contexts contents Richard Haines
2021-12-08 20:11 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 5/7] policy_config_files.md: Update openssh_contexts contents Richard Haines
2021-12-08 20:12 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 6/7] policy_config_files.md: Update snapperd_contexts contents Richard Haines
2021-12-08 20:13 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 7/7] title.md: Clarify example code location Richard Haines
2021-12-08 20:14 ` Paul Moore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211208121654.7591-4-richard_c_haines@btinternet.com \
--to=richard_c_haines@btinternet.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.