From: Daniel Burgener <dburgener@linux.microsoft.com>
To: Paul Moore <paul@paul-moore.com>,
selinux@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] selinux: remove the runtime disable functionality
Date: Fri, 17 Mar 2023 16:25:18 -0400 [thread overview]
Message-ID: <7b02ffaa-d9ce-d75d-1078-cd1691f1230f@linux.microsoft.com> (raw)
In-Reply-To: <20230317195615.281810-1-paul@paul-moore.com>
On 3/17/2023 3:56 PM, Paul Moore wrote:
> --- a/Documentation/ABI/obsolete/sysfs-selinux-disable
> +++ b/Documentation/ABI/removed/sysfs-selinux-disable
> @@ -4,6 +4,9 @@ KernelVersion: 2.6.12-rc2 (predates git)
> Contact: selinux@vger.kernel.org
> Description:
>
> + REMOVAL UPDATE: The SELinux checkreqprot functionality was removed in
> + March 2023, the original deprecation notice is shown below.
> +
> The selinuxfs "disable" node allows SELinux to be disabled at runtime
> prior to a policy being loaded into the kernel. If disabled via this
> mechanism, SELinux will remain disabled until the system is rebooted.
Looks like a copy/paste typo from the other deprecation removal. I
assume this should mention runtime disable, rather than checkreqprot.
-Daniel
next prev parent reply other threads:[~2023-03-17 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 19:56 [PATCH] selinux: remove the runtime disable functionality Paul Moore
2023-03-17 20:25 ` Daniel Burgener [this message]
2023-03-17 20:43 ` Paul Moore
2023-03-17 23:15 ` Casey Schaufler
2023-03-20 16:17 ` Paul Moore
2023-03-18 7:42 ` Ondrej Mosnacek
2023-03-20 16:24 ` Paul Moore
2023-03-20 15:14 ` Mickaël Salaün
2023-03-20 16:31 ` Paul Moore
2023-03-20 16:36 ` 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=7b02ffaa-d9ce-d75d-1078-cd1691f1230f@linux.microsoft.com \
--to=dburgener@linux.microsoft.com \
--cc=linux-security-module@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).