From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Julien Grall <julien.grall@linaro.org>, selinux@tycho.nsa.gov
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH 2/4] Add device tree ocontext nodes to Xen policy
Date: Thu, 12 Mar 2015 13:32:14 -0400 [thread overview]
Message-ID: <5501CD9E.4020805@tycho.nsa.gov> (raw)
In-Reply-To: <5501CC8B.2040303@linaro.org>
On 03/12/2015 01:27 PM, Julien Grall wrote:
> Hi Daniel,
>
> On 12/03/15 17:12, Daniel De Graaf wrote:
>> ;
>> +dtree_context_def : DEVICETREECON path security_context_def
>> + {if (define_devicetree_context()) return -1;}
>> + ;
>
> The regex for matching the device tree path is different from a path.
>
> the pathname convention is:
>
> node-name@unit-address
>
> The characters allowed for node-name/unit-name are:
> 0-9 a-z A-Z , . _ + -
>
> Although the @unit-address may be ommitted.
>
> So the regex should be something like:
> "/"({alnum}|['\._\+\-@])*
This is addressed in patch 4, where a quoted version of the path
expression is added which allows these characters (and others).
--
Daniel De Graaf
National Security Agency
WARNING: multiple messages have this Message-ID (diff)
From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Julien Grall <julien.grall@linaro.org>, selinux@tycho.nsa.gov
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/4] Add device tree ocontext nodes to Xen policy
Date: Thu, 12 Mar 2015 13:32:14 -0400 [thread overview]
Message-ID: <5501CD9E.4020805@tycho.nsa.gov> (raw)
In-Reply-To: <5501CC8B.2040303@linaro.org>
On 03/12/2015 01:27 PM, Julien Grall wrote:
> Hi Daniel,
>
> On 12/03/15 17:12, Daniel De Graaf wrote:
>> ;
>> +dtree_context_def : DEVICETREECON path security_context_def
>> + {if (define_devicetree_context()) return -1;}
>> + ;
>
> The regex for matching the device tree path is different from a path.
>
> the pathname convention is:
>
> node-name@unit-address
>
> The characters allowed for node-name/unit-name are:
> 0-9 a-z A-Z , . _ + -
>
> Although the @unit-address may be ommitted.
>
> So the regex should be something like:
> "/"({alnum}|['\._\+\-@])*
This is addressed in patch 4, where a quoted version of the path
expression is added which allows these characters (and others).
--
Daniel De Graaf
National Security Agency
next prev parent reply other threads:[~2015-03-12 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 17:12 [PATCH 0/4] Xen/FLASK policy updates for device contexts Daniel De Graaf
2015-03-12 17:12 ` [PATCH 1/4] Expand Xen IOMEMCON to 64 bits Daniel De Graaf
2015-03-12 17:12 ` Daniel De Graaf
2015-03-12 17:34 ` [Xen-devel] " Julien Grall
2015-03-12 17:34 ` Julien Grall
2015-03-12 17:12 ` [PATCH 2/4] Add device tree ocontext nodes to Xen policy Daniel De Graaf
2015-03-12 17:12 ` Daniel De Graaf
2015-03-12 17:27 ` [Xen-devel] " Julien Grall
2015-03-12 17:27 ` Julien Grall
2015-03-12 17:32 ` Daniel De Graaf [this message]
2015-03-12 17:32 ` Daniel De Graaf
2015-03-12 18:04 ` [Xen-devel] " Julien Grall
2015-03-12 18:04 ` Julien Grall
2015-03-12 17:12 ` [PATCH 3/4] checkpolicy: add output for Xen policy version support Daniel De Graaf
2015-03-12 17:12 ` Daniel De Graaf
2015-03-12 17:43 ` Stephen Smalley
2015-03-12 17:43 ` Stephen Smalley
2015-03-12 17:12 ` [PATCH 4/4] checkpolicy: Expand allowed character set in paths Daniel De Graaf
2015-03-12 17:12 ` Daniel De Graaf
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=5501CD9E.4020805@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=julien.grall@linaro.org \
--cc=selinux@tycho.nsa.gov \
--cc=xen-devel@lists.xenproject.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 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.