| 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
| ||
|
Message-Id: <1205513878.22912.68.camel@moss-spartans.epoch.ncsc.mil> Date: Fri, 14 Mar 2008 12:57:58 -0400 From: Stephen Smalley <sds@...ch.ncsc.mil> To: "Serge E. Hallyn" <serue@...ibm.com> Cc: Pavel Emelyanov <xemul@...nvz.org>, Greg KH <greg@...ah.com>, James Morris <jmorris@...ei.org>, lkml <linux-kernel@...r.kernel.org>, linux-security-module@...r.kernel.org, Casey Schaufler <casey@...aufler-ca.com> Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2) On Fri, 2008-03-14 at 10:45 -0500, Serge E. Hallyn wrote: > Quoting Pavel Emelyanov (xemul@...nvz.org): > > [snip] > > > > >> My main question was why was that file in the kernel/ directory? > > >> Shouldn't that also be in the security/ directory? > > > > > > I'm using cgroups to track the tasks which should have their device > > > permissions restricted. Right now cgroups are all under kernel/. > > > > No. Memory cgroup is under mm/ :) > > Ah. > > Guess it could all go under security/. Should it still go there even if > we make it not use lsm? There is the precedent of the security/keys directory (security-related, but not using LSM - aside from calling LSM hooks for access checks and labeling of keys). -- Stephen Smalley National Security Agency -- 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/
Powered by blists - more mailing lists