linux-kernel - Re: [RFC] cgroups: implement device whitelist lsm (v2)

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]

Date:	Thu, 13 Mar 2008 17:46:17 -0500
From:	"Serge E. Hallyn" <serue@...ibm.com>
To:	James Morris <jmorris@...ei.org>
Cc:	"Serge E. Hallyn" <serue@...ibm.com>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-security-module@...r.kernel.org, Greg KH <greg@...ah.com>,
	Stephen Smalley <sds@...ch.ncsc.mil>,
	Casey Schaufler <casey@...aufler-ca.com>,
	Pavel Emelianov <xemul@...nvz.org>
Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2)

Quoting James Morris (jmorris@...ei.org):
> On Thu, 13 Mar 2008, Serge E. Hallyn wrote:
> 
> > True, but while this change simplifies the code a bit, the semantics
> > seem more muddled - devcg will be enforcing when CONFIG_CGROUP_DEV=y
> > and:
> > 
> > 	SECURITY=n or
> > 	rootplug is enabled
> > 	capabilities is enabled
> > 	smack is enabled
> > 	selinux+capabilities is enabled
> 
> Well, this is how real systems are going to be deployed.

Sorry, do you mean with capabilities?

> It becomes confusing, IMHO, if you have to change which secondary LSM you 
> stack with SELinux to enable a cgroup feature.

So you're saying selinux without capabilities should still be able to
use dev_cgroup?  (Just making sure I understand right)

-serge
--
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/