From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at token ':' on line 6727:
Date: Tue, 29 Sep 2009 09:38:49 -0700 [thread overview]
Message-ID: <4AC23819.5020604@gmail.com> (raw)
In-Reply-To: <1254238109.10232.117.camel@gorn.columbia.tresys.com>
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
prev parent reply other threads:[~2009-09-29 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 15:09 [refpolicy] policy/modules/kernel/corenetwork.te":1722:ERROR 'syntax error' at token ':' on line 6727: Justin Mattock
2009-09-29 15:28 ` Christopher J. PeBenito
2009-09-29 16:38 ` Justin P. Mattock [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=4AC23819.5020604@gmail.com \
--to=justinmattock@gmail.com \
--cc=refpolicy@oss.tresys.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.