All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Musgrave" <dmusgrave@abodiosoftware.com>
To: "Stephen Smalley" <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re:  Invalid context in targeted SELinux policy
Date: Wed, 16 Aug 2006 15:21:45 +0000	[thread overview]
Message-ID: <W4127611390290341155741705@webmail11> (raw)

> role system_r types upgrade_t;

This did it; this isn't the first (and probably won't be the last) time that I've quickly read 'sysadm' and seen 'system'.

>Hmm...application_domain() includes a role statement for sysadm_r by
>default, and also includes a role statement for system_r if
>targeted_policy is defined, i.e. building targeted policy.  At least in
>the last release of the example policy.  But possibly that wasn't in the
>CentOS/RHEL policies as shipped.

It seems that in the global_macros.te supplied on this machine, the application_domain() only defines the sysadm_r role statement, while a later macro system_domain() defines system_r instead.  (And glancing at this second macro, it seems that it may be more appropriate for what I need anyway.)

Thanks very much for your help,

Daniel Musgrave
Abodio Software




--
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:[~2006-08-16 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 15:21 Daniel Musgrave [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-15 21:50 Invalid context in targeted SELinux policy Daniel Musgrave
2006-08-16 13:02 ` Karl MacMillan
2006-08-16 13:19   ` Karl MacMillan
2006-08-16 13:37   ` Erich Schubert
2006-08-16 13:24 ` Stephen Smalley

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=W4127611390290341155741705@webmail11 \
    --to=dmusgrave@abodiosoftware.com \
    --cc=sds@tycho.nsa.gov \
    --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.