All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: selinux@tycho.nsa.gov, selinux-dev@tresys.com
Subject: ANN: SELinux Policy Server Project
Date: Mon, 13 Dec 2004 15:45:00 -0500	[thread overview]
Message-ID: <41BDFF4C.1080109@tresys.com> (raw)
In-Reply-To: <20041210162047.HHLP7908.mm-ismta4.bizmailsrvcs.net@FLM800>

We at Tresys have started a project to design and implement an SELinux
policy server. This project, which builds on the recently completed
policy module project, will create a policy server that implements fine
grained access controls on the SELinux policy itself, as well as
implementing an infrastructure for userspace object managers and
eventually infrastructure for network policy management. The initial
release and design document is on the Tresys webpage at
http://www.tresys.com/selinux/.

The current release implements a hierarchal structure in policies
allowing, for example, types to have subtypes with less than or equal
permissions but not more. This was mentioned before on the SELinux list,
an archive of the thread is located at
http://marc.theaimsgroup.com/?l=selinux&m=109908469725763&w=2.

An application in policycoreutils/policy-verifier will verify that the
policy is internally consistant with the hierarchy. It is a standalone
application meant to be run on a kernel policy. Instructions for running
this verification step when a module is installed are included.

The compiler included in this release understands and stores hierarchal
symbols. This compiler is experimental, however. In order to gain
acceptance of this policy language change we have made a patch against
the existing policy compiler (included in this email). The patch allows
the '.' notation to be used for roles, types, object classes,
attributes, and aliases, which can then be verified with the
standalone verifier.

This project will be long term and experimental; therefore, we would
like to solicit community involvement, especially in the form of
feedback on the requirements, architecture, and design. A sourceforge
project for this has been created at
http://sourceforge.net/projects/sepolicy-server/ . We'll be keeping the
CVS repository there up to date with development and making regular
releases to the files area.


Joshua Brindle
Tresys Technology


diff -u -r1.6 policy_scan.l
--- checkpolicy/policy_scan.l   9 Aug 2004 18:12:29 -0000       1.6
+++ checkpolicy/policy_scan.l   10 Dec 2004 20:35:43 -0000
@@ -161,7 +161,7 @@
t2 |
T2                             { return(T2); }
"/"({letter}|{digit}|_|"."|"-"|"/")*   { return(PATH); }
-{letter}({letter}|{digit}|_)*  { return(IDENTIFIER); }
+{letter}({letter}|{digit}|_|".")*("*")?        { return(IDENTIFIER); }
{letter}({letter}|{digit}|_|"."|"-")*  { return(USER_IDENTIFIER); }
{digit}{digit}*                 { return(NUMBER); }
{hexval}{0,4}":"{hexval}{0,4}":"({hexval}|":"|".")*    {
return(IPV6_ADDR); }






--
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:[~2004-12-13 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041210162047.HHLP7908.mm-ismta4.bizmailsrvcs.net@FLM800>
2004-12-13 20:45 ` Joshua Brindle [this message]
2004-12-15 14:46   ` ANN: SELinux Policy Server Project Steve G
2004-12-15 15:15     ` 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=41BDFF4C.1080109@tresys.com \
    --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.