From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Daniel Musgrave <dmusgrave@abodiosoftware.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Invalid context in targeted SELinux policy
Date: Wed, 16 Aug 2006 09:02:57 -0400 [thread overview]
Message-ID: <1155733377.10971.2.camel@localhost.localdomain> (raw)
In-Reply-To: <W7685912732296271155678629@webmail16>
On Tue, 2006-08-15 at 21:50 +0000, Daniel Musgrave wrote:
> I am in the process of writing an application and associated policy in Centos 4.3, running a targeted SELinux environment at version 1.17.30-2.126. After succesfully creating the necessary rules in my .te file, and the associated file contexts in the .fc file, I am attempting to resolve one last problem. After compiling my policy and running the application, I get the following error:
>
> audit(...): security_compute_sid: invalid context root:system_r:upgrade_t for scontext=root:system_r:unconfined_t tcontext=system_u:object_r:upgrade_exec_t tclass=process
>
> The domain for this executable is 'upgrade' and the file context of the binary is 'upgrade_exec_t' (there are some associated *_log_t and *_tmp_t files as well). The .te file defines upgrade using the application_domain macro.
>
Did you authorize your type for the system_r role?
role system_r upgrade_t;
Karl
--
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.
next prev parent reply other threads:[~2006-08-16 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 21:50 Invalid context in targeted SELinux policy Daniel Musgrave
2006-08-16 13:02 ` Karl MacMillan [this message]
2006-08-16 13:19 ` Karl MacMillan
2006-08-16 13:37 ` Erich Schubert
2006-08-16 13:24 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2006-08-16 15:21 Daniel Musgrave
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=1155733377.10971.2.camel@localhost.localdomain \
--to=kmacmillan@mentalrootkit.com \
--cc=dmusgrave@abodiosoftware.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.