SELinux-Refpolicy Archive mirror
 help / color / mirror / Atom feed
From: Chris PeBenito <pebenito@ieee.org>
To: refpolicy <selinux-refpolicy@vger.kernel.org>, selinux@vger.kernel.org
Subject: ANN: Reference Policy 2.20200229
Date: Sat, 29 Feb 2020 19:23:05 -0500	[thread overview]
Message-ID: <3d857ac3-616c-072e-6a86-3b715eb8e00f@ieee.org> (raw)

This release includes several new modules:
  - cryfs
  - consolesetup
  - knot
  - tpm2
  - wireguard

Changes:
  - *_var_run_t types are renamed to *_runtime_t to remove the path
    from the type name
  - Added inotify watch permissions defined and added to systemd and
    other common services
  - Defined perf_event object class
  - Reimplemented fc_sort in Python
  - Added file contexts lint tool in Travis CI build
  - Updated Vagrant tooling for refpolicy testing on Fedora and Debian
    VMs
  - Added general interfaces for systemd bind mount points
  - Many more minor fixes across the policy

Removals:
  - Removed obsolete permissions


<https://github.com/SELinuxProject/refpolicy/releases/tag/RELEASE_2_20200229>

-- 
Chris PeBenito

                 reply	other threads:[~2020-03-01  0:23 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=3d857ac3-616c-072e-6a86-3b715eb8e00f@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).