All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: selinux <selinux@tycho.nsa.gov>
Cc: selinux-dev@tresys.com
Subject: [Patch 0/3] Loadable policy module infrastructure
Date: Thu, 26 May 2005 13:26:59 -0400	[thread overview]
Message-ID: <1117128419.3482.18.camel@localhost> (raw)

These patches provide the infrastructure to implement loadable policy
modules in the SELinux policy compiler. They add all the module data
structures and changes to checkpolicy to build a policy by reading the
policy.conf into the module structures and then expand it into the
current policy format. This will add everything we need to implement the
loadable modules in a subsequent patch.

We attempted to match the upstream compiler behavior completely and so
there are parts of the patch that implements inconsistent logic (such as
type conflict handling for conditionals) that we plan on cleaning up
later and making consistent. 

Aside from policies with large amounts of conditional rules the policies
generated by this compiler and the current policy compiler will be
identical, this ensures that correct policies are being built. The
conditional rules are ordered differently by this patch because of the
way the conditional expressions are optimized. The policy itself is
semantically identical however.

Also, we have tested MLS policy generation and it seems to work but we'd
like some indication from someone running an MLS system that it indeed
does work correctly.

We expect to send additional patches soon; one which implements the
module language itself and another to remove * and ~ from allow rules
per a previous thread on this list.


Joshua Brindle
Tresys Technology


--
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:[~2005-05-26 17:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1117128419.3482.18.camel@localhost \
    --to=jbrindle@tresys.com \
    --cc=selinux-dev@tresys.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.