Thread (45 messages) 45 messages, 4 authors, 2018-09-21

[PATCH security-next v2 19/26] LSM: Introduce CONFIG_LSM_ORDER

From: casey@schaufler-ca.com (Casey Schaufler)
Date: 2018-09-21 00:14:45
Also in: linux-arch, linux-doc, lkml

On 9/20/2018 5:10 PM, Casey Schaufler wrote:
On 9/20/2018 9:23 AM, Kees Cook wrote:
quoted
This provides a way to declare LSM initialization order via Kconfig.

Signed-off-by: Kees Cook <redacted>
---
 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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help