From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: ANN: SELinux userspace 3.2-rc2 release candidate
Date: Wed, 03 Feb 2021 11:58:18 +0100 [thread overview]
Message-ID: <87lfc5mn91.fsf@redhat.com> (raw)
Hello,
A 3.2-rc2 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-rc1
----------------------------------
* Improved usability of `getseuser`
* Fixed several issues in cil code found by OSS-FUZZ
* `setfiles` doesn't abort on labeling errors
* libsemanage tries to sync data to prevent empty files in SELinux module store
Development-relevant changes since 3.2-rc1
------------------------------------------
* `scripts/release` was improved to be more robust and release a source repository
Packaging-relevant changes since 3.2-rc1
----------------------------------------
* Source repository snapshot selinux-3.2-rc2.tar.gz is available on the release page
Shortlog of changes since the 3.2-rc1 release
-----------------------------------------------
Christian Göttsche (2):
libselinux: accept const fromcon in get_context API
libselinux: update getseuser
James Carter (3):
libsepol/cil: Update symtab nprim field when adding or removing datums
libsepol/cil: Fix heap-use-after-free in __class_reset_perm_values()
libsepol/cil: Fix heap-use-after-free when using optional blockinherit
Nicolas Iooss (4):
GitHub Actions: run SELinux testsuite in Fedora virtual machine
libsepol/cil: fix memory leak when a constraint expression is too deep
libsepol/cil: unlink blockinherit->block link when destroying a block
scripts/release: make the script more robust, and release a source repository snapshot
Petr Lautrbach (5):
setfiles: Do not abort on labeling error
setfiles: drop ABORT_ON_ERRORS and related code
libsemanage: sync filesystem with sandbox
policycoreutils/setfiles: Drop unused nerr variable
Update VERSIONs to 3.2-rc2 for release.
Vit Mojzis (1):
python/sepolgen: allow any policy statement in if(n)def
reply other threads:[~2021-02-03 10:59 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=87lfc5mn91.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