All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] new svn refpolicy difficuties:
Date: Tue, 02 Dec 2008 08:13:21 -0500	[thread overview]
Message-ID: <1228223603.9691.19.camel@gorn> (raw)
In-Reply-To: <1228112352.3841.13.camel@unix>

On Sun, 2008-11-30 at 22:19 -0800, Justin P. Mattock wrote:
> With the latest refpolicy, I'm 
> able to have all of the allow rules
> during the boot process applied to the policy,
> but as soon as I add any of the allow rules
> after startx, with any role I'm denied 
> with building the policy i.g.
> 
> :ERROR 'type staff_dbusd_t is not within scope' at token ';' on line
> 2581459:
> 
> I think this has to do with my policy/users
> file.(where can I find info on setting a prefix?)

I suspect it is actually related to this:

http://marc.info/?l=selinux&m=122477138927253&w=2

What changes have you made (if any) to the policy?  Also the
policy/modules.conf and build.conf?

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

  reply	other threads:[~2008-12-02 13:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01  6:19 [refpolicy] new svn refpolicy difficuties: Justin P. Mattock
2008-12-02 13:13 ` Christopher J. PeBenito [this message]
2008-12-02 15:57   ` Justin P. Mattock
2008-12-02 18:53     ` Christopher J. PeBenito
2008-12-02 19:41       ` Justin P. Mattock
2008-12-03 13:22         ` Christopher J. PeBenito
2008-12-03 16:49           ` Justin Mattock
2008-12-03 20:30             ` Christopher J. PeBenito
2008-12-03 21:06               ` Justin Mattock
2008-12-04 20:50                 ` Justin Mattock
2008-12-03  0:03       ` Justin Mattock
2008-12-02 17:31   ` Justin P. Mattock

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=1228223603.9691.19.camel@gorn \
    --to=cpebenito@tresys.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.