keywords in .fc files

keywords in .fc files

[Colin Powers]

Hi all,

We are trying in a .fc file to assign a label to a directory path containing the word 'include', e.g.

/opt/mydir/include(/.*)?		-d	gen_context(system_u:object_r:my_context_t,s0)

However it seems 'include(...)' is interpreted as a keyword/macro which causes a compilation error:
`/.*': No such file or directory

Is there a way around this, other than by doing something funny with the regex, like wildcarding one of the letters?

Cheers
Colin

Re: keywords in .fc files

[Stephen Smalley]

On 02/11/2015 05:57 AM, Colin Powers wrote:
> Hi all,
> 
> We are trying in a .fc file to assign a label to a directory path containing the word 'include', e.g.
> 
> /opt/mydir/include(/.*)?		-d	gen_context(system_u:object_r:my_context_t,s0)
> 
> However it seems 'include(...)' is interpreted as a keyword/macro which causes a compilation error:
> `/.*': No such file or directory
> 
> Is there a way around this, other than by doing something funny with the regex, like wildcarding one of the letters?

I'm guessing that this is a result of passing the .fc file through m4 to
expand macros like gen_context().  So perhaps you could just quote it to
avoid expansion by m4?

Re: keywords in .fc files

[Christopher J. PeBenito]

On 2/11/2015 5:57 AM, Colin Powers wrote:
> Hi all,
> 
> We are trying in a .fc file to assign a label to a directory path containing the word 'include', e.g.
> 
> /opt/mydir/include(/.*)?		-d	gen_context(system_u:object_r:my_context_t,s0)
> 
> However it seems 'include(...)' is interpreted as a keyword/macro which causes a compilation error:
> `/.*': No such file or directory
> 
> Is there a way around this, other than by doing something funny with the regex, like wildcarding one of the letters?

You can do a "stupid m4 trick", by adding in an empty string
(backtick-apostraphe) before the open parenthesis:

/opt/mydir/include`'(/.*)?


For example:

$ cat test
/opt/mydir/include`'(/.*)?

$ m4 test
/opt/mydir/include(/.*)?


Note: Reference Policy questions should be asked on the refpolicy list
(http://oss.tresys.com/mailman/listinfo/refpolicy)

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com