From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
James Morris <jmorris@namei.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Stephen Smalley <sds@epoch.ncsc.mil>,
Casey Schaufler <casey@schaufler-ca.com>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2)
Date: Fri, 14 Mar 2008 08:54:16 -0500 [thread overview]
Message-ID: <20080314135416.GD8744@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20080314044741.GB18077@kroah.com>
Quoting Greg KH (greg@kroah.com):
> On Thu, Mar 13, 2008 at 08:41:21PM -0500, Serge E. Hallyn wrote:
> > Quoting James Morris (jmorris@namei.org):
> > > On Thu, 13 Mar 2008, Serge E. Hallyn wrote:
> > >
> > > > Quoting James Morris (jmorris@namei.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?
> > >
> > > Yes.
> > >
> > > All Fedora, RHEL, CentOS etc. ship with SELinux+capabilities. I can't
> > > imagine not enabling them on other kernels.
> > >
> > > > > 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)
> > >
> > > Nope, SELinux always stacks with capabilities, so havng the cgroup hooks
> > > in capabilities makes sense (rather than having us change the secondary
> > > stacking LSM just to enable a feature).
> >
> > Oh, ok.
> >
> > Will let the patch stand until Pavel and Greg comment then.
>
> 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/.
> And to be honest, I didn't really look at it at all other than the
> diffstat to make sure you weren't messing with the kobj_map stuff
> anymore :)
>
> thanks,
>
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-14 13:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 3:27 Serge E. Hallyn
2008-03-13 9:25 ` James Morris
2008-03-13 13:18 ` Serge E. Hallyn
2008-03-13 13:50 ` James Morris
2008-03-13 14:38 ` Serge E. Hallyn
2008-03-13 22:27 ` James Morris
2008-03-13 22:46 ` Serge E. Hallyn
2008-03-13 23:49 ` James Morris
2008-03-14 1:41 ` Serge E. Hallyn
2008-03-14 4:47 ` Greg KH
2008-03-14 13:54 ` Serge E. Hallyn [this message]
2008-03-14 13:58 ` Pavel Emelyanov
2008-03-14 15:45 ` Serge E. Hallyn
2008-03-14 15:54 ` Pavel Emelyanov
2008-03-14 16:57 ` Stephen Smalley
2008-03-14 9:28 ` Pavel Emelyanov
2008-03-14 13:58 ` Serge E. Hallyn
2008-03-14 14:05 ` Pavel Emelyanov
2008-03-14 14:37 ` Serge E. Hallyn
2008-03-14 15:07 ` Pavel Emelyanov
2008-03-14 14:12 ` Paul Menage
2008-03-14 14:42 ` Serge E. Hallyn
2008-03-16 0:59 ` Paul Menage
2008-03-14 2:51 ` Casey Schaufler
2008-03-14 9:16 ` Paul Menage
2008-03-14 14:05 ` Serge E. Hallyn
2008-03-14 14:15 ` Paul Menage
2008-03-14 14:35 ` Serge E. Hallyn
2008-03-16 0:57 ` Paul Menage
2008-03-14 9:18 ` Paul Menage
2008-03-14 14:00 ` Serge E. Hallyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080314135416.GD8744@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=greg@kroah.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®