From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Cc: Laine Stump <laine@redhat.com>
Subject: [PATCH 0/6] selinux: Assorted fixes, libvirt support
Date: Tue, 21 Feb 2023 19:39:09 +0100 [thread overview]
Message-ID: <20230221183915.3740123-1-sbrivio@redhat.com> (raw)
This series exports interfaces that are useful for libvirt, updates
type enforcement rules to current needs, and fixes some issues.
Stefano Brivio (6):
selinux/passt.if: Fix typo in passt_read_data interface definition
selinux: Define interfaces for libvirt and similar frameworks
selinux: Switch to a more reasonable model for PID and socket files
selinux/passt.te: Allow setcap on the process itself
selinux/passt.te: Allow /etc/resolv.conf symlinks to be followed
selinux/passt.te: Allow setting socket option on routing netlink
socket
contrib/selinux/passt.fc | 1 -
contrib/selinux/passt.if | 28 +++++++++++++++++++++++++++-
contrib/selinux/passt.te | 16 +++++++++++-----
3 files changed, 38 insertions(+), 7 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-21 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 18:39 Stefano Brivio [this message]
2023-02-21 18:39 ` [PATCH 1/6] selinux/passt.if: Fix typo in passt_read_data interface definition Stefano Brivio
2023-02-21 18:39 ` [PATCH 2/6] selinux: Define interfaces for libvirt and similar frameworks Stefano Brivio
2023-02-21 18:39 ` [PATCH 3/6] selinux: Switch to a more reasonable model for PID and socket files Stefano Brivio
2023-02-21 18:39 ` [PATCH 4/6] selinux/passt.te: Allow setcap on the process itself Stefano Brivio
2023-02-21 18:39 ` [PATCH 5/6] selinux/passt.te: Allow /etc/resolv.conf symlinks to be followed Stefano Brivio
2023-02-21 18:39 ` [PATCH 6/6] selinux/passt.te: Allow setting socket option on routing netlink socket Stefano Brivio
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=20230221183915.3740123-1-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=laine@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).