This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] xen/xsm/flask: Fix permission tables

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xen/xsm/flask: Fix permission tables
From: Stephen Smalley <sds@xxxxxxxxxxxxx>
Date: Mon, 11 Apr 2011 10:32:15 -0400
Cc: Xen <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 11 Apr 2011 07:33:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19875.3337.398308.78362@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: National Security Agency
References: <1296665024.26511.14.camel@moss-pluto> <19875.3337.398308.78362@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2011-04-11 at 15:15 +0100, Ian Jackson wrote:
> Stephen Smalley writes ("[Xen-devel] [PATCH] xen/xsm/flask: Fix permission 
> tables"):
> > Fix this by updating the flask config and regenerating the headers from
> > it.  In the future, this can be further improved by integrating the
> > automatic generation of the headers into the build process as is
> > presently done in SELinux.
> What rune, tool or Makefile target did you use to regenerate the
> headers ?

$ make -C tools/flask/policy/policy/flask
$ install -m 644 tools/flask/policy/policy/flask/*.h xen/xsm/flask/include/

Stephen Smalley
National Security Agency

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>