From: Russell Coker <russell@coker.com.au>
To: Michael Graffam <michael.graffam@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: New to SELinux -- any suggestions?
Date: Sun, 29 Oct 2006 15:01:18 +1000 [thread overview]
Message-ID: <200610291601.19715.russell@coker.com.au> (raw)
In-Reply-To: <1162096212.15530.22.camel@endless>
On Sunday 29 October 2006 15:30, Michael Graffam <michael.graffam@gmail.com>
wrote:
> > The problem here is your idea of "removing the permission". Chcon does
> > not add or remove permissions, it merely changes the labels of files.
> > What the label means is determined by the policy.
> >
> > So if you want to change a file back to it's default context you can
> > use "restorecon", in this case "restorecon -F -R -v /usr/local /usr/bin"
> > should do what you want.
>
> 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.
SE Linux does not support multiple contexts on one object. If multiple
contexts are supported then it becomes almost impossible to analyse the
policy. For example if we want to make sure that domain user_t can not write
to any file that allows a domain transition to a domain that can write to
the /etc/shadow file (shadow_t) then we need to make sure that there is no
file type which is an entry point for passwd_t that is also writable by
user_t, this is a fairly simple analysis to perform.
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).
> > Another option is to know what the original context was (maybe by
> > examining the file with "ls -Z" before changing it in the first place).
> > In this case I know that the bin directories have type bin_t, so the
> > following would work: chcon -t bin_t /usr/bin/sbcl /usr/local/bin/lisp
>
> 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.
--
russell@coker.com.au
http://etbe.blogspot.com/ My Blog
http://www.coker.com.au/sponsorship.html Sponsoring Free Software development
--
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-10-29 5:01 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 [this message]
2006-10-29 6:05 ` Michael Graffam
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=200610291601.19715.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=michael.graffam@gmail.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.