From: Chris PeBenito <pebenito@ieee.org>
To: refpolicy <selinux-refpolicy@vger.kernel.org>,
SElinux list <selinux@vger.kernel.org>
Subject: ANN: Reference Policy 2.20220106
Date: Thu, 6 Jan 2022 14:42:07 -0500 [thread overview]
Message-ID: <14da8945-fc25-7361-6840-c5f4640dac77@ieee.org> (raw)
https://github.com/SELinuxProject/refpolicy/releases/tag/RELEASE_2_20220106
Notable changes:
* Module versions were dropped. Policy module versions were removed in semodule
many years ago, so they no longer serve a purpose in the policy. The
policy_module() macro still supports the version argument. If it is missing,
a default version is set, to satisfy the policy syntax.
* The MCS constraints changed to reflect the usage in systems, primarily for
separating containers and VMs. To separate a domain by MCS it will now need
to opt in using the mcs_constrained() interface.
* New support for grouping user domains and their surrogates, e.g. user_t
surrogates user_wm_t and user_systemd_t, such that allowing the user domain
to domain transition to a child domain will be allowed for surrogate domains.
See pull requests #365 and #381 for more information.
New module:
- obfs4proxy
--
Chris PeBenito
reply other threads:[~2022-01-06 19:42 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=14da8945-fc25-7361-6840-c5f4640dac77@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 read-only IMAP folder(s) and NNTP newsgroup(s).