All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <lautrbach@redhat.com>
To: SElinux list <selinux@vger.kernel.org>
Subject: ANN: SELinux userspace 3.11-rc3 release
Date: Wed, 24 Jun 2026 21:34:17 +0200	[thread overview]
Message-ID: <878q83u406.fsf@redhat.com> (raw)

Hello!

The 3.11-rc3 release for the SELinux userspace is now available at:

https://github.com/SELinuxProject/selinux/releases/tag/3.11-rc3
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.

Unless something unexpected happen, 3.11 will be released
next week. Also only important patches will be merged before the
release.

User-visible changes since 3.11-rc3
-----------------------------------
- Bug fixes

Development-relevant changes
----------------------------

- Improved CI
- Added EXTRA_LD_FLAGS for use by musl+llvm builds to pass --undefined-version.

Shortlog of the changes since 3.11-rc2 release
----------------------------------------------
Chris PeBenito (2):
      CI: Fix variable use in build-userspace action.
      CI: Add explicit output variable for build-userspace action.

Christian Göttsche (3):
      secilc/docs: fix wrong CIL statements
      secilc/docs: mention nlmsg extended permissions
      Makefile: avoid 0 as NULL pointer constant

James Carter (2):
      libsepol: Check for proper length of addr and mask buffers
      secilc: Use fstat instead of stat to avoid TOCTOU issues

Kalevi Kolttonen (16):
      libselinux: use null character with strings
      policycoreutils: use stderr for error messages
      policycoreutils: use null character in a string
      policycoreutils: use null character in strings
      policycoreutils: check strdup() failure
      policycoreutils: use null character in a string
      policycoreutils: use bool instead of int
      policycoreutils: use null character in a string
      policycoreutils: use bool instead of int
      mcstrans: use null character in strings
      mcstrans: use null character in strings
      sandbox: use bool instead of int
      audit2allow: make error message more helpful
      policycoreutils: use bool instead of int
      mcstrans: use sig_atomic_t and bool instead of int
      libsepol: Add missing comment to context.h

Petr Lautrbach (1):
      Update VERSIONs to 3.11-rc3 for release.

Stephen Smalley (2):
      python/semanage: do not leak an audit fd per logger instance
      libselinux: Add EXTRA_LD_FLAGS for musl+llvm builds

netliomax25-code (11):
      libsepol: fix out-of-bounds typealias_lists access in module_to_cil
      libsepol: cast to unsigned char in ctype calls
      libsepol: null-terminate temporary buffer in mls_to_string
      libsepol: bound category values in mls_semantic_level_expand
      libsemanage: guard end of path in semanage_fc_find_meta
      libsepol: bound type values in type_set_expand negset loop
      libsepol: test type_set_expand bounds negset type values
      libsepol/cil: fix double free of borrowed type datum on error path
      mcstrans: fix out-of-bounds read in parse_raw sensitivity parsing
      checkpolicy: fix xperm complement at range boundaries
      checkpolicy: reject out-of-range extended permission values


                 reply	other threads:[~2026-06-24 19:34 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=878q83u406.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.