linux-kernel - [PATCH -rt] panic on SLIM + selinux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061230154804.862606000@mvista.com>
Date:	Sat, 30 Dec 2006 07:48:04 -0800
From:	Daniel Walker <dwalker@...sta.com>
To:	akpm@...l.org
CC:	Kylene Hall <kjhall@...ibm.com>
Subject: [PATCH -rt] panic on SLIM + selinux

If you have both SLIM and selinux compiled into your kernel selinux will panic
if it can't register itself. The code below, 

if (register_security (&selinux_ops))
	panic("SELinux: Unable to register with kernel.\n");

"security/selinux/hooks.c" 5014 lines --95%--                                                                           4811,35       96%

This could be a bug report cause I bet there's a better way to make these mutually 
exclusive.

Signed-Off-By: Daniel Walker <dwalker@...sta.com>

---
 security/slim/Kconfig |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6.19/security/slim/Kconfig
===================================================================
--- linux-2.6.19.orig/security/slim/Kconfig
+++ linux-2.6.19/security/slim/Kconfig
@@ -1,6 +1,6 @@
 config SECURITY_SLIM
 	boolean "SLIM support"
-	depends on SECURITY && SECURITY_NETWORK && INTEGRITY
+	depends on SECURITY && SECURITY_NETWORK && INTEGRITY && !SECURITY_SELINUX
 	help
 	  The Simple Linux Integrity Module implements a modified low water-mark
 	  mandatory access control integrity model.
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/