From: Kenton Groombridge <me@concord.sh>
To: selinux-refpolicy@vger.kernel.org
Cc: Kenton Groombridge <me@concord.sh>
Subject: [PATCH 4/7] mcs: constrain misc IPC objects
Date: Fri, 29 Oct 2021 17:04:40 -0400 [thread overview]
Message-ID: <20211029210443.17461-5-me@concord.sh> (raw)
In-Reply-To: <20211029210443.17461-1-me@concord.sh>
Signed-off-by: Kenton Groombridge <me@concord.sh>
---
policy/mcs | 3 +++
1 file changed, 3 insertions(+)
diff --git a/policy/mcs b/policy/mcs
index 8db3838f5..6207b2734 100644
--- a/policy/mcs
+++ b/policy/mcs
@@ -123,6 +123,9 @@ mlsconstrain { tcp_socket udp_socket rawip_socket sctp_socket } node_bind
mlsconstrain key { create link read search setattr view write }
(( h1 dom h2 ) or ( t1 != mcs_constrained_type ));
+mlsconstrain { ipc sem msgq shm } { create destroy setattr write unix_write }
+ (( h1 dom h2 ) or ( t1 != mcs_constrained_type ));
+
#
# MCS policy for SELinux-enabled databases
#
--
2.33.1
next prev parent reply other threads:[~2021-10-29 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 21:04 [PATCH 0/7] mcs, various: pull in changes from Fedora policy Kenton Groombridge
2021-10-29 21:04 ` [PATCH 1/7] mcs: deprecate mcs overrides Kenton Groombridge
2021-10-29 21:04 ` [PATCH 2/7] mcs: restrict create, relabelto on mcs files Kenton Groombridge
2021-10-29 21:04 ` [PATCH 3/7] mcs: add additional constraints to databases Kenton Groombridge
2021-10-29 21:04 ` Kenton Groombridge [this message]
2021-10-29 21:04 ` [PATCH 5/7] mcs: combine single-level object creation constraints Kenton Groombridge
2021-10-29 21:04 ` [PATCH 6/7] various: deprecate mcs override interfaces Kenton Groombridge
2021-10-29 21:04 ` [PATCH 7/7] corenet: make netlabel_peer_t mcs constrained Kenton Groombridge
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=20211029210443.17461-5-me@concord.sh \
--to=me@concord.sh \
--cc=selinux-refpolicy@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).