From: Chris PeBenito <pebenito@ieee.org>
To: SElinux list <selinux@vger.kernel.org>,
refpolicy <selinux-refpolicy@vger.kernel.org>
Subject: ANN: Reference Policy 2.20200818
Date: Tue, 18 Aug 2020 09:47:39 -0400 [thread overview]
Message-ID: <a22aa5ab-8f26-dfd5-5834-44d0393b9708@ieee.org> (raw)
New modules:
- usbguard
- aptcacher
Changes:
- Renamed "pid" interfaces to "runtime" interfaces to match the *_var_run_t to
*_runtime_t rename
- Merge systemd generator domains
- Several systemd updates
- Set value of build options to "true" so m4 ifelse can be used
- Revise relabeling access to prevent relabeling to unlabeled_t
- Makefile, Vagrant, and m4 improvements
- First pass of cleanups from SELint
- Clean up domains that had user tty or pty access but could be used from
either
- Add various inotify watch permissions
- Add rules for apt-catcher-ng and acngtool
- Add support for generating nft tables to gennetfilter
- Many more minor fixes across the policy
Removals:
- Drop Python 2 compatibility code from genhomedircon.py
- Remove unlabeled packet access
- Remove ada module
https://github.com/SELinuxProject/refpolicy/releases/tag/RELEASE_2_20200818
--
Chris PeBenito
reply other threads:[~2020-08-18 13:47 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=a22aa5ab-8f26-dfd5-5834-44d0393b9708@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).