[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.21.1810040427550.13517@namei.org>
Date: Thu, 4 Oct 2018 04:28:07 +1000 (AEST)
From: James Morris <jmorris@...ei.org>
To: Kees Cook <keescook@...omium.org>
cc: John Johansen <john.johansen@...onical.com>,
Jordan Glover <Golden_Miller83@...tonmail.ch>,
Stephen Smalley <sds@...ho.nsa.gov>,
Paul Moore <paul@...l-moore.com>,
Casey Schaufler <casey@...aufler-ca.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
"Schaufler, Casey" <casey.schaufler@...el.com>,
linux-security-module <linux-security-module@...r.kernel.org>,
Jonathan Corbet <corbet@....net>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH security-next v4 23/32] selinux: Remove boot parameter
On Wed, 3 Oct 2018, Kees Cook wrote:
> On Wed, Oct 3, 2018 at 11:17 AM, James Morris <jmorris@...ei.org> wrote:
> > On Tue, 2 Oct 2018, John Johansen wrote:
> >> To me a list like
> >> lsm.enable=X,Y,Z
> >
> > What about even simpler:
> >
> > lsm=selinux,!apparmor,yama
>
> We're going to have lsm.order=, so I'd like to keep it with a dot
> separator (this makes it more like module parameters, too). You want
> to mix enable/disable in the same string? That implies you'd want
> implicit enabling (i.e. it complements the builtin enabling), which is
> opposite from what John wanted.
>
Why can't this be the order as well?
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists