From: Stephen Smalley <sds@tycho.nsa.gov>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Xen <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen/xsm/flask: Fix permission tables
Date: Mon, 11 Apr 2011 10:32:15 -0400 [thread overview]
Message-ID: <1302532335.7338.39.camel@moss-pluto> (raw)
In-Reply-To: <19875.3337.398308.78362@mariner.uk.xensource.com>
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
prev parent reply other threads:[~2011-04-11 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 16:43 [PATCH] xen/xsm/flask: Fix permission tables Stephen Smalley
2011-04-11 14:15 ` Ian Jackson
2011-04-11 14:32 ` Stephen Smalley [this message]
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=1302532335.7338.39.camel@moss-pluto \
--to=sds@tycho.nsa.gov \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.