[refpolicy] policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at token ':' on line 6727:

[refpolicy] policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at token ':' on line 6727:

[Justin Mattock]

Seems I hit this on a random:

Compiling refpolicy policy.22
/usr/bin/checkpolicy -c 22  -U deny policy.conf -o policy.22
/usr/bin/checkpolicy:  loading policy configuration from policy.conf
policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at
token ':' on line 6727:

doing a git clean -fx fixes this.

why/how is corenetwork.te(or something network.te) being created?

-- 
Justin P. Mattock

[refpolicy] policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at token ':' on line 6727:

[Christopher J. PeBenito]

On Tue, 2009-09-29 at 08:09 -0700, Justin Mattock wrote:
> Seems I hit this on a random:
> 
> Compiling refpolicy policy.22
> /usr/bin/checkpolicy -c 22  -U deny policy.conf -o policy.22
> /usr/bin/checkpolicy:  loading policy configuration from policy.conf
> policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at
> token ':' on line 6727:
> 
> doing a git clean -fx fixes this.
> 
> why/how is corenetwork.te(or something network.te) being created?

Refpolicy creates it from corenetwork.te.in.  We generate it because
interfaces for nodes, ports, netifs, and packets are easy to create, and
we add them all the time.

Without more information on the error, I can't say any more.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150

[refpolicy] policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at token ':' on line 6727:

[Justin P. Mattock]

Christopher J. PeBenito wrote:
> On Tue, 2009-09-29 at 08:09 -0700, Justin Mattock wrote:
>    
>> Seems I hit this on a random:
>>
>> Compiling refpolicy policy.22
>> /usr/bin/checkpolicy -c 22  -U deny policy.conf -o policy.22
>> /usr/bin/checkpolicy:  loading policy configuration from policy.conf
>> policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at
>> token ':' on line 6727:
>>
>> doing a git clean -fx fixes this.
>>
>> why/how is corenetwork.te(or something network.te) being created?
>>      
>
> Refpolicy creates it from corenetwork.te.in.  We generate it because
> interfaces for nodes, ports, netifs, and packets are easy to create, and
> we add them all the time.
>
> Without more information on the error, I can't say any more.
>
>    
That's fine.(this was all the info from the error
that I can see)
I'm wondering if I'm missing something during
my build of policycoreutils. looking at where there error
is happening:
allow corenet_unconfined_type node_type:node *;
seems ":" is confusing checkpolicy

Maybe there's a python-doc/xml package I missed
causing checkpolicy to not know what to do with
":" in certain situations..

In any case other than that everything seems to be o.k.
At the moment I have two machines(as a test) running the
latest refpolicy/userspace tools with ipsec  transactions
between the two.(pretty cool how the policy shows
the info from setkeys)

Justin P. Mattock