From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: SELinux List <selinux@tycho.nsa.gov>
Subject: ANN: SETools 4.0.0-alpha2
Date: Wed, 11 Feb 2015 10:48:35 -0500 [thread overview]
Message-ID: <54DB79D3.8@tresys.com> (raw)
Tresys has released SETools 4.0.0-alpha2:
https://github.com/TresysTechnology/setools/releases/tag/4.0.0-alpha2
In this release, SETools has been updated to support Python 3 (tested
with 3.3 and 3.4) and includes travis-ci testing[1]. Many features are
complete or nearly complete (full list at the end of the email) and
available for use via the CLI tools. The GUI tools have not yet been
started.
Warning: If you replace the SETools 3.x on your system, it will break
the couple of tools from sepolgen/policycoreutils that depend on SETools
(e.g. sepolicy) since libqpol/libapol C libraries and their
corresponding SWIG wrappers are no longer provided.
If you are interested in contributing, GitHub's pull request feature is
preferred for submitting patches. Please include unit tests.
SETools requires the following development packages for building:
Python 2.7 or 3.3+
setuptools
gcc
bison
flex
libselinux
libsepol 2.4+
libbz2
SWIG 2.0.12+ or 3.0+
To run SETools, the following packages are required:
Python 2.7 or 3.3+
NetworkX 1.8+
setuptools
libselinux
libsepol 2.4+
libbz2
Completed (and nearly completed) features:
* TE rule query
* RBAC rule query
* MLS rule query (range_transition; except for range criteria)
* Type query
* Role query
* User query (except level/range criteria)
* Object class query
* Common query
* Boolean query
* Policy capability query
* All context queries (portcon, genfscon, etc, except range criteria)
* Information flow analysis
* Domain transition analysis
[1] https://travis-ci.org/TresysTechnology/setools
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next reply other threads:[~2015-02-11 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 15:48 Christopher J. PeBenito [this message]
2015-05-29 12:45 ` ANN: SETools 4.0.0-alpha2 Stephen Smalley
2015-05-29 14:42 ` Christopher J. PeBenito
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=54DB79D3.8@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.