From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: Question on unconfined_t
Date: Mon, 17 Nov 2014 23:42:25 +0100 [thread overview]
Message-ID: <20141117224224.GB7768@e145.network2> (raw)
In-Reply-To: <CAOK12DarQLB3QcmRLd4xTWTDS0kBD+zAXfh_0oHK3_gYxnniiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Mon, Nov 17, 2014 at 09:18:51PM +0000, Paddie O'Brien wrote:
> Thanks. I was under the mistaken impression that unconfined_t got
> something for free. My new understanding is that it's by convention
> that policy writers give access to unconfined_t to their domains and
> they do so by adding explicit rules.
>
> Also I was missing file_type(mytype_exec_t) although I had
> domain_type(mytpe_t). Is there a way to see what things like file_type
> and domain_type expand to? I want to know what's going on in the
> background.
>
Forgot the answer the actual question. You can look up what the various "macros" expand to by perusing /usr/share/selinux/devel/include if you have installed the selinux-policy-devel package
It might help a bit if you are familiar with m4. Its just macros that eventually expand to selinux policy language, sometimes the macros can nest pretty deep before you end up with the raw rules.
macros are basically yet another way to group even more ...
--
Dominick Grift
[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]
prev parent reply other threads:[~2014-11-17 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 14:44 Question on unconfined_t Paddie O'Brien
2014-11-17 15:37 ` Stephen Smalley
2014-11-17 20:37 ` Daniel J Walsh
2014-11-17 21:18 ` Paddie O'Brien
2014-11-17 21:54 ` Dominick Grift
2014-11-17 22:42 ` Dominick Grift [this message]
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=20141117224224.GB7768@e145.network2 \
--to=dac.override@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.