SELinux Security Module development
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: ANN: SELinux userspace 3.2-rc3 release candidate
Date: Wed, 24 Feb 2021 16:45:54 +0100	[thread overview]
Message-ID: <87v9ah1nbh.fsf@redhat.com> (raw)

Hello,

A 3.2-rc3 release candidate for the SELinux userspace is now 
available at:

https://github.com/SELinuxProject/selinux/wiki/Releases

Please give it a test and let us know if there are any issues.

If there are specific changes that you think should be called out 
in release notes for packagers and users in the final release
announcement, let us know. 

Thanks to all the contributors to this release candidate!

User-visible changes since 3.2-rc2
----------------------------------

* Improved secilc documentation - fenced code blocks, syntax highlighting, custom
  color theme, ...

* Better error reporting in getconlist

* Improved selinux(8,5) and fixiles(8) man pages

* Bug fixes

Packaging-relevant changes since 3.2-rc2
----------------------------------------

* sestatus is installed as /usr/bin/sestatus by default. Original /usr/sbin/sestatus is
  a relative symlink to the /usr/bin/sestatus.


Shortlog of changes since the 3.2-rc2 release
-----------------------------------------------
Christian Göttsche (3):
      libselinux/getconlist: report failures
      policycoreutils/fixfiles.8: add missing file systems and merge check and verify
      libsepol/cil: handle SID without assigned context when writing policy.conf

Dominick Grift (1):
      secilc: fixes cil_role_statements.md example

James Carter (4):
      libsepol/cil: Fix integer overflow in the handling of hll line marks
      libsepol/cil: Destroy disabled optional blocks after pass is complete
      libsepol: Create function ebitmap_highest_set_bit()
      libsepol: Validate policydb values when reading binary policy

Nicolas Iooss (7):
      libsepol: remove unused files
      libsepol: uniformize prototypes of sepol_mls_contains and sepol_mls_check
      libsepol: include header files in source files when matching declarations
      libsepol/cil: fix NULL pointer dereference with empty macro argument
      libsepol/cil: be more robust when encountering <src_info>
      libsepol/cil: introduce intermediate cast to silence -Wvoid-pointer-to-enum-cast
      libselinux: rename gettid() to something which never conflicts with the libc

Petr Lautrbach (3):
      libselinux: fix segfault in add_xattr_entry()
      policycoreutils: Resolve path in restorecon_xattr
      Update VERSIONs to 3.2-rc3 for release.

Vit Mojzis (2):
      selinux(8,5): Describe fcontext regular expressions
      gui: fix "file type" selection in fcontextPage

bauen1 (4):
      secilc/docs: use fenced code blocks for cil examples
      secilc/docs: add syntax highlighting for secil
      secilc/docs: add custom color theme
      policycoreutils: sestatus belongs to bin not sbin


             reply	other threads:[~2021-02-24 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 15:45 Petr Lautrbach [this message]
2021-02-24 17:29 ` ANN: SELinux userspace 3.2-rc3 release candidate - the last one Petr Lautrbach

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=87v9ah1nbh.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --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