All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Graffam <michael.graffam@gmail.com>
To: russell@coker.com.au
Cc: selinux@tycho.nsa.gov
Subject: Re: New to SELinux -- any suggestions?
Date: Sun, 29 Oct 2006 01:05:58 -0500	[thread overview]
Message-ID: <1162101958.2580.10.camel@endless> (raw)
In-Reply-To: <200610291601.19715.russell@coker.com.au>

On Sun, 2006-10-29 at 15:01 +1000, Russell Coker wrote:
> On Sunday 29 October 2006 15:30, Michael Graffam <michael.graffam@gmail.com> 
> wrote:
> > Thank you for the help. Can one AND/OR the contexts? Based on the above,
> > it would seem to me that if an executable violated two points of policy
> > it wouldn't be possible to 'bless' it -- since I'm sure this isn't the
> > case, I'm wondering how I might apply multiple contexts. Or am I still
> > out in left field here?
> 
> I don't know what you mean by "bless" in this message.

By "bless" I meant "Allow it to run regardless." Or "Give it the
blessing to misbehave."


> If however a file could have multiple types then such analysis would be 
> impossible unless you also had rules determining which pairs of contexts 
> might be applied to one file (in which case every permitted pair of contexts 
> could be mapped to a single context in the current SE Linux system for the 
> same result).

OK, that makes perfect sense. I had figured that multiple contexts would
be allowed, to prevent the possible need of expanding the number of
required 'base' contexts. But, I can certainly see your point about the
difficulty of analyzing all possible combinations. 

> > Whooo.. new ls fields too! Man, I feel like a kid again! This is
> > great! :) Having been using GNU/Linux for so long, I almost forgot how
> > fun it is to learn new stuff about it!
> 
> There is also "id -Z", "ps -Z" and "cp -Z".  There are also a few new 
> commands, in addition to chcon there's runcon and newrole (which isn't being 
> used so much nowadays) and there is semanage and getsebool/setsebool to 
> manage it.

Thanks again for your help. Would you happen to know if there is a
document somewhere which gives a general overview of the structure of
the SELinux mechanisms, maybe with some details on the common contexts
and so forth?

-M


--
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-10-29  6:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29  1:41 New to SELinux -- any suggestions? Michael Graffam
2006-10-29  3:31 ` Russell Coker
2006-10-29  4:30   ` Michael Graffam
2006-10-29  5:01     ` Russell Coker
2006-10-29  6:05       ` Michael Graffam [this message]
2006-10-29  6:47         ` Russell Coker
2006-10-29 16:08         ` Joshua Brindle

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=1162101958.2580.10.camel@endless \
    --to=michael.graffam@gmail.com \
    --cc=russell@coker.com.au \
    --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.