Return-Path: <linux-kernel-owner+w=401wt.eu-S1757324AbYCNOAm@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757324AbYCNOAm (ORCPT <rfc822;w@1wt.eu>);
	Fri, 14 Mar 2008 10:00:42 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752815AbYCNOAe
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 14 Mar 2008 10:00:34 -0400
Received: from e34.co.us.ibm.com ([32.97.110.152]:53812 "EHLO
	e34.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752789AbYCNOAe (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 14 Mar 2008 10:00:34 -0400
Date: Fri, 14 Mar 2008 09:00:31 -0500
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Paul Menage <menage@google.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>, lkml <linux-kernel@vger.kernel.org>,
       linux-security-module@vger.kernel.org, Greg KH <greg@kroah.com>,
       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)
Message-ID: <20080314140031.GF8744@sergelap.austin.ibm.com>
References: <20080313032749.GA13258@sergelap.austin.ibm.com> <6599ad830803140218v3d9ca478ve41516a9ea627eb@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6599ad830803140218v3d9ca478ve41516a9ea627eb@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1795
Lines: 42

Quoting Paul Menage (menage@google.com):
> On Wed, Mar 12, 2008 at 8:27 PM, Serge E. Hallyn <serue@us.ibm.com> wrote:
> > Implement a cgroup using the LSM interface to enforce mknod and open
> >  on device files.
> >
> >  This implements a simple device access whitelist.  A whitelist entry
> >  has 4 fields.  'type' is a (all), c (char), or b (block).  'all' means it
> >  applies to all types, all major numbers, and all minor numbers.  Major and
> >  minor are obvious.  Access is a composition of r (read), w (write), and
> >  m (mknod).
> >
> >  The root devcgroup starts with rwm to 'all'.  A child devcg gets a copy
> >  of the parent.  Admins can then add and remove devices to the whitelist.
> >  Once CAP_HOST_ADMIN is introduced it will be needed to add entries as
> >  well or remove entries from another cgroup, though just CAP_SYS_ADMIN
> >  will suffice to remove entries for your own group.
> >
> >  An entry is added by doing "echo <type> <maj> <min> <access>" > devcg.allow,
> >  for instance:
> >
> >         echo b 7 0 mrw > /cgroups/1/devcg.allow
> >
> >  An entry is removed by doing likewise into devcg.deny.  Since this is a
> >  pure whitelist, not acls, you can only remove entries which exist in the
> >  whitelist.  You must explicitly
> >
> >         echo a 0 0 mrw > /cgroups/1/devcg.deny
> >
> >  to remove the "allow all" entry which is automatically inherited from
> >  the root cgroup.
> 
> In keeping with the naming convention for control groups, "devices"
> would be better than "devcg".

Noted, thanks.

-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/