All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hung Truong <hung.truong@tridsys.com>
To: SELinux <selinux@tycho.nsa.gov>
Subject: ERROR 'type staff_java_t is not within scope' at token
Date: Mon, 21 Jan 2013 13:40:50 -0500	[thread overview]
Message-ID: <bf19e346e82ccd053990b576f4058a61@mail.gmail.com> (raw)
In-Reply-To: 3086262d0228a121663cb87f5d77a07a@mail.gmail.com

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

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

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

             reply	other threads:[~2013-01-21 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 18:40 Hung Truong [this message]
2013-01-21 22:26 ` ERROR 'type staff_java_t is not within scope' at token Dominick Grift
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=bf19e346e82ccd053990b576f4058a61@mail.gmail.com \
    --to=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.