ERROR 'syntax error' at token ':c' on line 42:

ERROR 'syntax error' at token ':c' on line 42:

[Justin Mattock]

This is also hitting when building a module for the policy(below)
basically start the system(opensuse 11.4) then do:

dmesg > dmesg
audit2allow -i dmesg -M Zonemod
compilation failed:
Zonemod.te:42:ERROR 'syntax error' at token ':c' on line 42:
allow auditd_t device_t:chr_file { read write open };
#============= auditd_t ==============
/usr/bin/checkmodule:  error(s) encountered while parsing configuration
/usr/bin/checkmodule:  loading policy configuration from Zonemod.te

ended up copying audit.log, messages, dmesg to another machine to make
the modules
then installed them on the machine that's produces this error, just to
get up and running
in enforcement mode.

let me know what I can do.

-- 
Justin P. Mattock

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

[refpolicy] ERROR 'syntax error' at token ':c' on line 42:

[Justin Mattock]

This is also hitting when building a module for the policy(below)
basically start the system(opensuse 11.4) then do:

dmesg > dmesg
audit2allow -i dmesg -M Zonemod
compilation failed:
Zonemod.te:42:ERROR 'syntax error' at token ':c' on line 42:
allow auditd_t device_t:chr_file { read write open };
#============= auditd_t ==============
/usr/bin/checkmodule:  error(s) encountered while parsing configuration
/usr/bin/checkmodule:  loading policy configuration from Zonemod.te

ended up copying audit.log, messages, dmesg to another machine to make
the modules
then installed them on the machine that's produces this error, just to
get up and running
in enforcement mode.

let me know what I can do.

-- 
Justin P. Mattock

Re: [refpolicy] ERROR 'syntax error' at token ':c' on line 42:

[Christopher J. PeBenito]

On 10/10/10 02:17, Justin Mattock wrote:
> This is also hitting when building a module for the policy(below)
> basically start the system(opensuse 11.4) then do:
>
> dmesg>  dmesg
> audit2allow -i dmesg -M Zonemod
> compilation failed:
> Zonemod.te:42:ERROR 'syntax error' at token ':c' on line 42:
> allow auditd_t device_t:chr_file { read write open };
> #============= auditd_t ==============
> /usr/bin/checkmodule:  error(s) encountered while parsing configuration
> /usr/bin/checkmodule:  loading policy configuration from Zonemod.te

What are the lines above that one that supposedly has an error?

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

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

[refpolicy] ERROR 'syntax error' at token ':c' on line 42:

[Christopher J. PeBenito]

On 10/10/10 02:17, Justin Mattock wrote:
> This is also hitting when building a module for the policy(below)
> basically start the system(opensuse 11.4) then do:
>
> dmesg>  dmesg
> audit2allow -i dmesg -M Zonemod
> compilation failed:
> Zonemod.te:42:ERROR 'syntax error' at token ':c' on line 42:
> allow auditd_t device_t:chr_file { read write open };
> #============= auditd_t ==============
> /usr/bin/checkmodule:  error(s) encountered while parsing configuration
> /usr/bin/checkmodule:  loading policy configuration from Zonemod.te

What are the lines above that one that supposedly has an error?

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

Re: [refpolicy] ERROR 'syntax error' at token ':c' on line 42:

[Justin P. Mattock]

  On 10/11/2010 05:29 AM, Christopher J. PeBenito wrote:
> On 10/10/10 02:17, Justin Mattock wrote:
>> This is also hitting when building a module for the policy(below)
>> basically start the system(opensuse 11.4) then do:
>>
>> dmesg>  dmesg
>> audit2allow -i dmesg -M Zonemod
>> compilation failed:
>> Zonemod.te:42:ERROR 'syntax error' at token ':c' on line 42:
>> allow auditd_t device_t:chr_file { read write open };
>> #============= auditd_t ==============
>> /usr/bin/checkmodule:  error(s) encountered while parsing configuration
>> /usr/bin/checkmodule:  loading policy configuration from Zonemod.te
>
> What are the lines above that one that supposedly has an error?
>


the lines above this are:

     class dir { write read search add_name };
}

#============= auditd_t ==============
allow auditd_t device_t:chr_file { read write open };

which seems to be o.k. from over here.

here is dmesg, and some other info:
http://fpaste.org/2ptC/

Justin P. Mattock



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

[refpolicy] ERROR 'syntax error' at token ':c' on line 42:

[Justin P. Mattock]

  On 10/11/2010 05:29 AM, Christopher J. PeBenito wrote:
> On 10/10/10 02:17, Justin Mattock wrote:
>> This is also hitting when building a module for the policy(below)
>> basically start the system(opensuse 11.4) then do:
>>
>> dmesg>  dmesg
>> audit2allow -i dmesg -M Zonemod
>> compilation failed:
>> Zonemod.te:42:ERROR 'syntax error' at token ':c' on line 42:
>> allow auditd_t device_t:chr_file { read write open };
>> #============= auditd_t ==============
>> /usr/bin/checkmodule:  error(s) encountered while parsing configuration
>> /usr/bin/checkmodule:  loading policy configuration from Zonemod.te
>
> What are the lines above that one that supposedly has an error?
>


the lines above this are:

     class dir { write read search add_name };
}

#============= auditd_t ==============
allow auditd_t device_t:chr_file { read write open };

which seems to be o.k. from over here.

here is dmesg, and some other info:
http://fpaste.org/2ptC/

Justin P. Mattock

Re: ERROR 'syntax error' at token ':c' on line 42:

[Stephen Smalley]

Looks like the previously discussed flex bug, e.g.:
http://marc.info/?l=selinux&m=126763385807985&w=2

On Sun, Oct 10, 2010 at 2:17 AM, Justin Mattock <justinmattock@gmail.com> wrote:
> This is also hitting when building a module for the policy(below)
> basically start the system(opensuse 11.4) then do:
>
> dmesg > dmesg
> audit2allow -i dmesg -M Zonemod
> compilation failed:
> Zonemod.te:42:ERROR 'syntax error' at token ':c' on line 42:
> allow auditd_t device_t:chr_file { read write open };
> #============= auditd_t ==============
> /usr/bin/checkmodule:  error(s) encountered while parsing configuration
> /usr/bin/checkmodule:  loading policy configuration from Zonemod.te
>
> ended up copying audit.log, messages, dmesg to another machine to make
> the modules
> then installed them on the machine that's produces this error, just to
> get up and running
> in enforcement mode.
>
> let me know what I can do.
>
> --
> Justin P. Mattock
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
>


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: ERROR 'syntax error' at token ':c' on line 42:

[Justin P. Mattock]

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

  On 10/12/2010 04:39 AM, Stephen Smalley wrote:
> Looks like the previously discussed flex bug, e.g.:
> http://marc.info/?l=selinux&m=126763385807985&w=2
>

yeah I was thinking this as well.. from what it seems this is hitting 
with the
packages provided by suse,  as well as the userspace packages. but unlike
my other system that was hitting this, the error is with building a 
module, instead of building
the policy.(as a workaround I would throw in an older version of flex, 
then build only
checkpolicy/module to get it working..(or if I was too lazy just copy a 
version that
works over to the other machine)).

I can go through this today and see what I get.. one thing I noticed 
with the packages
from suse(11.4) is, policycoreutils is older than same of the newer 
packages they have,
causing other errors with python i.e. seinfo not found kind of error.

As for flex itself.. I do remember starting a bisect on that package, 
but then realized
that from version 2.34(if I remember correctly) to 2.35 theirs just a 
few patches that
are rather lengthy, making a bisect possible, but then going through the 
bad commit
more lengthy...

Justin P. Mattock



[-- Attachment #2: Type: text/html, Size: 1941 bytes --]

[refpolicy] ERROR 'syntax error' at token ':c' on line 42:

[Justin P. Mattock]

  On 10/12/2010 04:39 AM, Stephen Smalley wrote:
> Looks like the previously discussed flex bug, e.g.:
> http://marc.info/?l=selinux&m=126763385807985&w=2
>

yeah I was thinking this as well.. from what it seems this is hitting 
with the
packages provided by suse,  as well as the userspace packages. but unlike
my other system that was hitting this, the error is with building a 
module, instead of building
the policy.(as a workaround I would throw in an older version of flex, 
then build only
checkpolicy/module to get it working..(or if I was too lazy just copy a 
version that
works over to the other machine)).

I can go through this today and see what I get.. one thing I noticed 
with the packages
from suse(11.4) is, policycoreutils is older than same of the newer 
packages they have,
causing other errors with python i.e. seinfo not found kind of error.

As for flex itself.. I do remember starting a bisect on that package, 
but then realized
that from version 2.34(if I remember correctly) to 2.35 theirs just a 
few patches that
are rather lengthy, making a bisect possible, but then going through the 
bad commit
more lengthy...

Justin P. Mattock


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.tresys.com/pipermail/refpolicy/attachments/20101012/46fd43a0/attachment.html