All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: <selinux@tycho.nsa.gov>
Subject: ANN: SETools 4 open-sourced
Date: Tue, 8 Jul 2014 15:04:46 -0400	[thread overview]
Message-ID: <53BC40CE.4040206@tresys.com> (raw)

Tresys has open-sourced SETools 4, available on GitHub:

https://github.com/TresysTechnology/setools

The current development state is alpha; this is a reimplementation of
SETools using Python.  Only CLI tools have been implemented so far, but
the GUI tools will eventually return.  Presently, the code uses SETools
3's libqpol library (with SWIG wrapper) to provide the low-level access
to the binary policy file.  Going forward, we'd like to propose an
upstream library which would provide a low-level policy query interface;
this could be useful for other tools such as dispol and sepolicy-analyze
(from the seandroid repo).

The focus of the effort thus far has been:
* Implement core functionality
* Implement unit testing

There are functional versions (with varying completeness) of the
following tools:
* sedta (a new CLI tool for domain transition analysis)
* seinfo
* seinfoflow (a new CLI tool for information flow analysis)
* sesearch

To use SETools 4, the following packages are required:
* Python 2.7
* sepolgen
* NetworkX
* SETools 3 libraries w/Python wrappers (git version)

To install SETools or run the unit tests, the Python setuptools package
is also required.

The TODO list is still lengthy, but here are a few major areas that need
attention:
* complete the Python policy representation classes (e.g. users,
constraints, etc.)
* comprehensive component queries (role query, user query, class query,
etc.)
* full permission map handling (e.g. find permissions in policy that are
unmapped, save to file)

If you are interested in contributing, GitHub's pull request feature is
strongly preferred for submitting patches, but patches can also be sent
to this mail list.  Please include unit tests.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

                 reply	other threads:[~2014-07-08 19:05 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=53BC40CE.4040206@tresys.com \
    --to=cpebenito@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.