From: Paul Moore <paul@paul-moore.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Stephen Smalley <stephen.smalley.work@gmail.com>,
SElinux list <selinux@vger.kernel.org>
Subject: Re: [RFC PATCH] selinux: runtime disable is deprecated, add some ssleep() discomfort
Date: Fri, 12 Jun 2020 15:28:26 -0400 [thread overview]
Message-ID: <CAHC9VhQ25U5PLYMAA1onNssWrOMYrUXhfJ_SRpzM1qNXeavfuw@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNuWNw+e23_Lz0WN-=HODHmbSAmMQcAX87tVRGp3ZSiccA@mail.gmail.com>
On Thu, Jun 11, 2020 at 9:29 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> Good point about the installer. I have already started working on
> preparing Fedora for the runtime disable removal, but so far I'm only
> at the beginning. Updating anaconda to add selinux=0 to the kernel
> params instead of using /etc/selinux/config will be one of the main
> steps.
...
> I also prefer to rather go somewhere in this direction rather than
> introducing the delay. I was kinda OK with the delay at first, but as
> Stephen points out, it would punish users rather than distros, even
> though users are (normally) not the ones that make a conscious
> decision to use the runtime disable.
...
> Yes, I was under the impression that some changes in libselinux are
> needed before this works transparently, but apparently it already does
> the right thing now. In that case I'd say that it may be better to
> skip adding sleeps etc. and just remove the feature at some point. But
> please let's wait with that for a while longer so we can prepare
> Fedora for it first. It's hard to tell at this point how long that
> will take, but it could be several months.
>
> Then again, the sleep might be helpful to wake up potential non-Fedora
> users (if any) and in Fedora we can always apply a revert as a
> downstream patch until things are sorted. So if you guys really want
> it, I think we can deal with it.
I'm glad to hear Fedora is making changes to move away from the
runtime disable, please keep us updated about once a month so we know
where things are at with Fedora.
As I mentioned previously, I'm okay with postponing the delay so long
as Fedora is making progress - and according to Ondrej they are - so
I'm okay with holding off for now.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2020-06-12 19:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 12:47 [RFC PATCH] selinux: runtime disable is deprecated, add some ssleep() discomfort Paul Moore
2020-06-02 12:49 ` Paul Moore
2020-06-04 14:49 ` Stephen Smalley
2020-06-08 21:35 ` Paul Moore
2020-06-08 22:13 ` Stephen Smalley
2020-06-08 22:56 ` William Roberts
2020-06-10 14:03 ` Stephen Smalley
2020-06-10 14:11 ` Stephen Smalley
2020-06-11 13:29 ` Ondrej Mosnacek
2020-06-12 19:28 ` Paul Moore [this message]
2020-08-19 17:14 ` Petr Lautrbach
2020-08-19 19:07 ` Stephen Smalley
2020-08-19 19:16 ` Stephen Smalley
2020-08-20 15:41 ` Casey Schaufler
2020-08-20 16:58 ` Stephen Smalley
2020-08-20 20:31 ` Petr Lautrbach
2020-09-10 11:39 ` Ondrej Mosnacek
2020-09-10 12:33 ` Stephen Smalley
2020-09-23 18:32 ` Paul Moore
2020-09-24 23:42 ` Stephen Smalley
2020-09-10 13:31 ` Stephen Smalley
2020-09-10 14:36 ` Stephen Smalley
2020-09-10 14:54 ` Stephen Smalley
2020-06-12 19:00 ` Paul Moore
2020-06-12 18:56 ` Paul Moore
2022-03-01 22:53 Paul Moore
2022-03-01 22:57 ` Paul Moore
2022-03-01 23:02 ` Casey Schaufler
2022-04-04 20:23 ` 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=CAHC9VhQ25U5PLYMAA1onNssWrOMYrUXhfJ_SRpzM1qNXeavfuw@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=omosnace@redhat.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
/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).