[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <17226f0a-e320-dab0-8691-aa0a22f07544@schaufler-ca.com>
Date: Thu, 20 Sep 2018 17:14:35 -0700
From: Casey Schaufler <casey@...aufler-ca.com>
To: Kees Cook <keescook@...omium.org>, James Morris <jmorris@...ei.org>
Cc: John Johansen <john.johansen@...onical.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Paul Moore <paul@...l-moore.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
"Schaufler, Casey" <casey.schaufler@...el.com>,
LSM <linux-security-module@...r.kernel.org>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH security-next v2 19/26] LSM: Introduce CONFIG_LSM_ORDER
On 9/20/2018 5:10 PM, Casey Schaufler wrote:
> On 9/20/2018 9:23 AM, Kees Cook wrote:
>> This provides a way to declare LSM initialization order via Kconfig.
>>
>> Signed-off-by: Kees Cook <keescook@...omium.org>
>> ---
>> security/Kconfig | 11 +++++++++++
>> security/security.c | 38 +++++++++++++++++++++++++++++++++++---
>> 2 files changed, 46 insertions(+), 3 deletions(-)
>>
>> diff --git a/security/Kconfig b/security/Kconfig
>> index 27d8b2688f75..de8202886c1d 100644
>> --- a/security/Kconfig
>> +++ b/security/Kconfig
>> @@ -276,5 +276,16 @@ config DEFAULT_SECURITY
>> default "apparmor" if DEFAULT_SECURITY_APPARMOR
>> default "" if DEFAULT_SECURITY_DAC
>>
>> +config LSM_ORDER
>> + string "Default initialization order of builtin LSMs"
>> + default "integrity"
> I would like to see the default spelled out rather than
> provided implicitly.
>
> + default "integrity,yama,loadpin,selinux,smack,apparmor,tomoyo"
I see now that comes later in the patch set. Never mind.
Powered by blists - more mailing lists