All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dominick.grift@gmail.com>
To: Hung Truong <hung.truong@tridsys.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: ERROR 'type staff_java_t is not within scope' at token
Date: Mon, 21 Jan 2013 23:26:00 +0100	[thread overview]
Message-ID: <1358807160.2986.7.camel@d30> (raw)
In-Reply-To: <bf19e346e82ccd053990b576f4058a61@mail.gmail.com>

On Mon, 2013-01-21 at 13:40 -0500, Hung Truong wrote:
> I have this rule in my policy:
> 
> 
> 
> gen_require(`
> 
>                 type staff_java_t;
> 
>                 type cdvoip_sysadmcat_pki_cdvaserver_pem_t;
> 
> ')
> 
> allow staff_java_t cdvoip_sysadmcat_pki_cdvaserver_pem_t: file { read open
> };
> 
> 
> 
> 
> 
> and get error 'type staff_java_t is not within scope'  when compile it.
> 
> 
> 
> 
> 
> policy/modules/cdvoip/cdvoip_sysadmcat.te":306:ERROR 'type staff_java_t is
> not within scope' at token ';' on line 1684769:
> 
> /usr/bin/checkpolicy:  loading policy configuration from policy.conf
> 
> allow staff_java_t cdvoip_sysadmcat_pki_cdvaserver_pem_t: file { read open
> };
> 
> 
> 
> checkpolicy:  error(s) encountered while parsing configuration
> 
> make: ***
> [/home/cdvadmin/workspace/cdvoip/rpms/BUILDROOT/selinux-policy-3.7.19-155el6.4.x86_64/etc/selinux/targeted/policy/policy.24]
> Error 1
> 
> 
> 
> 
> 
> Does anyone know why I get this error and how to fix it?  BTW, if it does
> matter, I modified the *.spec file to build a monolithic and strict policy.
> 

I think this policy needs to be nested properly

Its a dependency thing

so for example:

optional_policy(`
  java_per_role_template(staff, staff_r, staff_t)

  optional_policy(`
    allow staff_java_t cdvoip_sysadmcat_pki_cdvaserver_pem_t: file
read_file_perms;
  ')
')

This is just a quick example, it is missing requires and it might have
errors.

The point is that this is about dependencies and proper nesting. This
can get very complicated depending on the complexity of the policy.

The issue is that the type you are using (staff_java_t) depends on the
java_per_role_template so it needs to be nested in that call else it is
out of scope.

Welcome to the wonderful world of optional policy and role prefixed
domains

> 
> Many thanks,
> 
> Hung Truong
> I have this rule in my policy:
> 
>  
> 
> gen_require(`
> 
>                 type staff_java_t;
> 
>                 type cdvoip_sysadmcat_pki_cdvaserver_pem_t;
> 
> ')
> 
> allow staff_java_t cdvoip_sysadmcat_pki_cdvaserver_pem_t: file { read
> open };
> 
>  
> 
>  
> 
> and get error 'type staff_java_t is not within scope'  when compile
> it.
> 
>  
> 
>  
> 
> policy/modules/cdvoip/cdvoip_sysadmcat.te":306:ERROR 'type
> staff_java_t is not within scope' at token ';' on line 1684769:
> 
> /usr/bin/checkpolicy:  loading policy configuration from policy.conf
> 
> allow staff_java_t cdvoip_sysadmcat_pki_cdvaserver_pem_t: file { read
> open };
> 
>  
> 
> checkpolicy:  error(s) encountered while parsing configuration
> 
> make: ***
> [/home/cdvadmin/workspace/cdvoip/rpms/BUILDROOT/selinux-policy-3.7.19-155el6.4.x86_64/etc/selinux/targeted/policy/policy.24] Error 1
> 
>  
> 
>  
> 
> Does anyone know why I get this error and how to fix it?  BTW, if it
> does matter, I modified the *.spec file to build a monolithic and
> strict policy.
> 
>  
> 
> Many thanks,
> 
> Hung Truong
> 
>  
> 
> 



--
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.

  reply	other threads:[~2013-01-21 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 18:40 ERROR 'type staff_java_t is not within scope' at token Hung Truong
2013-01-21 22:26 ` Dominick Grift [this message]
2013-01-21 22:29   ` Dominick Grift
2013-01-21 22:39 ` Dominick Grift

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=1358807160.2986.7.camel@d30 \
    --to=dominick.grift@gmail.com \
    --cc=hung.truong@tridsys.com \
    --cc=selinux@tycho.nsa.gov \
    /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.