All of lore.kernel.org
 help / color / mirror / Atom feed
From: JW <jw@centraltexasit.com>
To: Stephen Smalley <sds@tislabs.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Is make relabel suposed to be run from policy or or setfiles?
Date: Tue, 9 Jul 2002 11:41:06 -0500	[thread overview]
Message-ID: <200207091141.06258.jw@centraltexasit.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0207090723320.27193-100000@raven>

On Tuesday 09 July 2002 06:49, you wrote:
> On Mon, 8 Jul 2002, JW wrote:
> > /usr/local/selinux/bin/setfiles:  invalid context
> > system_u:object_r:inetd_var_log_t on line number 625
> > /usr/local/selinux/bin/setfiles:  invalid context
> > system_u:object_r:initrc_runlevel_t on line number 669
>
> The types listed above are not defined in the upstream .te files nor are
> they used in the upstream .fc files.  So I'll assume that you are using a
> customized policy other than the example policy.  

Actually, no, at the time I was reciving those error messages, I was indeed using the default ploicy files, policy11.
I am running on SuSE 8.0 Most of those errors whent away when I added Carstens's additional policy files for SuSE. 

> In any event, the error is
> quite simple:  you are using types in your .fc files that are not defined
> in your .te files.

Ok, that is the information I was looking for.


> > Just out of curiosity, why do you have to be root to do that? 
>
 > You can login as a normal user initially, but you need to su to root.
> When running on a SELinux kernel, you also need to be in sysadm_r.

Presumeably you mean su and newrole. I haven't tried it yet, I will later.

> Keep in mind that the SELinux access controls are orthogonal to the Linux
> access controls, and that both access controls must authorize an operation
> in order for it to be performed.

Ok. I was under the impression (from things I read and heard), that root was pretty much reduced to a normal user, and the sysadm_* user became, in effect, root. 
But I'm still reading on the subject, hopefully there's something written about this in the documentation.

Thank you.

	JW



--
You have received this message because you are subscribed to the selinux 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:[~2002-07-09 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09  1:16 Is make relabel suposed to be run from policy or or setfiles? JW
2002-07-09  5:33 ` lsm3 notes Ed Street
2002-07-09 12:43   ` Stephen Smalley
2002-07-09 13:33     ` Ed Street
2002-07-09 14:03       ` Stephen Smalley
2002-07-09 11:49 ` Is make relabel suposed to be run from policy or or setfiles? Stephen Smalley
2002-07-09 16:41   ` JW [this message]
     [not found] <004f01c226f7$8f472fe0$0a01a8c0@ed>
2002-07-09  4:05 ` JW

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=200207091141.06258.jw@centraltexasit.com \
    --to=jw@centraltexasit.com \
    --cc=sds@tislabs.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.