selinux-refpolicy.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris PeBenito <pebenito@ieee.org>
To: SElinux list <selinux@vger.kernel.org>,
	refpolicy <selinux-refpolicy@vger.kernel.org>
Subject: ANN: SETools 4.3.0
Date: Wed, 1 Apr 2020 11:27:36 -0400	[thread overview]
Message-ID: <70175949-68b6-65da-f1a3-dc514ecf2fe1@ieee.org> (raw)

SETools 4.3.0 is now available:

https://github.com/SELinuxProject/setools/releases/tag/4.3.0

Changes since 4.2.2:

   * Revised sediff method for TE rules. This drastically reduced memory
     and run time.
   * Added infiniband context support to seinfo, sediff, and apol.
   * Added apol configuration for location of Qt assistant.
   * Fixed sediff issue where properties header would display when not
     requested.
   * Fixed sediff issue with type_transition file name comparison.
   * Fixed permission map socket sendto information flow direction.
   * Added methods to TypeAttribute class to make it a complete Python
     collection.
   * Genfscon now will look up classes rather than using fixed values
     which were dropped from libsepol.

-- 
Chris PeBenito

                 reply	other threads:[~2020-04-01 15:27 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=70175949-68b6-65da-f1a3-dc514ecf2fe1@ieee.org \
    --to=pebenito@ieee.org \
    --cc=selinux-refpolicy@vger.kernel.org \
    --cc=selinux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).