From: Petr Lautrbach <lautrbach@redhat.com>
To: selinux@vger.kernel.org
Subject: ANN: SELinux userspace 3.9-rc2 release
Date: Wed, 25 Jun 2025 19:49:36 +0200 [thread overview]
Message-ID: <87wm8ziudr.fsf@redhat.com> (raw)
Hello!
The 3.9-rc2 release for the SELinux userspace is now available at:
https://github.com/SELinuxProject/selinux/releases/tag/3.9-rc2
https://github.com/SELinuxProject/selinux/wiki/Releases
I signed all tarballs using my gpg key, see .asc files.
You can download the public key from
https://github.com/bachradsusi.gpg
Thanks to all the contributors, reviewers, testers and reporters!
If you miss something important not mentioned bellow, please let me
know.
User-visible changes
--------------------
* libsepol: Add new 'netif_wildcard' policy capability
* checkpolicy: Add support for wildcard netifcon names
* libsepol: Allow multiple policycap statements
* libsepol: Support genfs_seclabel_wildcard
* Replace all links to selinuxproject.org
* Bug fixes
Shortlog of the changes since 3.9-rc1 release
---------------------------------------------
Christian Göttsche (5):
libsepol: update sort order for netifcon definitions
libsepol: add netif_wildcard polcap
checkpolicy: add support for wildcard netifcon names
secilc/test: add test for wildcard netifcon statement
libsepol/cil: reject wildcard only network interface names
Inseob Kim (2):
libsepol: Allow multiple policycap statements
libsepol: Support genfs_seclabel_wildcard
James Carter (1):
libsemanage: Ignore missing field initializers in swig generated code
Petr Lautrbach (1):
Update VERSIONs to 3.9-rc2 for release.
Stephen Smalley (1):
userspace: replace all links to selinuxproject.org
reply other threads:[~2025-06-25 17:49 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=87wm8ziudr.fsf@redhat.com \
--to=lautrbach@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 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.