lkml.org 
[lkml]   [2018]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH security-next v2 19/26] LSM: Introduce CONFIG_LSM_ORDER
From
Date
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@chromium.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.

\
 
 \ /
  Last update: 2018-09-21 02:15    [W:0.054 / U:0.372 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site