All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Caplan <dac@tresys.com>
To: Dale Amon <amon@vnl.com>
Cc: "NSA's SELinux" <SELinux@tycho.nsa.gov>
Subject: Re: policy language extensions
Date: Fri, 26 Sep 2003 09:37:36 -0400	[thread overview]
Message-ID: <3F744120.6090509@tresys.com> (raw)
In-Reply-To: <20030926130232.GF10225@vnl.com>



Dale Amon wrote:
> 
> Some things could be difficult though: policy statements
> do not appear to me to have a 1:1 relation to the binary 
> representation.
> 

You are right, they do not.  The policy statement:

allow  domain  init_t : process  { sigchld signull };

expands into a hash table entry (in the binary policy) for every type 
associated with the domain attribute.  In a very stripped down policy I 
was looking at this was 49 types.

You also need to keep in mind that "subtraction" or disabling of rules, 
via a conditional policy, is not equivalent to removing permissions.  If 
the above rule were in a condition block that was disabled, there might 
still be an allow rule in the base policy, or even in another 
conditional block, that allowed those permissions.


-- 
__________________________________

David Caplan     410 290 1411 x105
dac@tresys.com
Tresys Technology, LLC
8840 Stanford Blvd., Suite 2100
Columbia, MD 21045


--
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:[~2003-09-26 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 21:45 policy language extensions David Caplan
2003-09-25 21:49 ` David Caplan
2003-09-26 13:02 ` Dale Amon
2003-09-26 13:37   ` David Caplan [this message]
2003-09-26 13:39   ` Stephen Smalley

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=3F744120.6090509@tresys.com \
    --to=dac@tresys.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=amon@vnl.com \
    /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.