linux-kernel - Re: [PATCH] Security: Add __init to register_security to disable load a security module on runtime

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201002281535.FIB29902.OLFQMHStJFOFOV@I-love.SAKURA.ne.jp>
Date:	Sun, 28 Feb 2010 15:35:30 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	wzt.wzt@...il.com
Cc:	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, sds@...ho.nsa.gov,
	jmorris@...ei.org
Subject: Re: [PATCH] Security: Add __init to register_security to disable load a security module on runtime

Zhitong Wang wrote:
> Load a security module on runtime is not safe on SMP systems,  LSM
> framework doesn't have any locks.

Unloading security module on runtime would be difficult. But loading security
module on runtime is not impossible. A security module can be loaded inside
initramfs if the security module provides appropriate lock.

When AppArmor get merged into mainline, do you want to bother distributors
about size of vmlinux when some wants to use SELinux, some wants to use Smack,
some wants to use TOMOYO, and some wants to use AppArmor. All of them have to
be built-in but only one of them can be enabled.

I think we should allow security modules to be loaded on runtime, if security
modules can provide appropriate lock for SMP-safe initialization.
--
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/