public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Milos Malik <mmalik@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: test if fapolicyd can talk to D-bus daemon
Date: Fri, 11 Sep 2026 13:18:21 GMT [thread overview]
Message-ID: <178913270100.1.7749888060309575103.tests-selinux-8c8d3ba91ee7@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : 8c8d3ba91ee770cf4c3e14aceab39a7d412e4b45
Author : Milos Malik <mmalik@redhat.com>
Date : 2020-10-20T19:09:39+00:00
Stats : +10/-0 in 2 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/8c8d3ba91ee770cf4c3e14aceab39a7d412e4b45?branch=pr775-checkpolicy-revdeps
Log:
test if fapolicyd can talk to D-bus daemon
Based on the content of reported SELinux denials, the fapolicyd
service (after its start) wants to communicate with D-bus daemon,
but SELinux policy does not allow that action. I believe this
behaviour is expected and it should be allowed in fapolicyd
SELinux module.
The automated TC looks for appropriate allow rules and it also
reproduces the issue.
The TC covers BZ#1874491.
---
diff --git a/selinux-policy/fapolicyd-and-similar/Makefile b/selinux-policy/fapolicyd-and-similar/Makefile
index d75d14e..aa9fa7a 100644
--- a/selinux-policy/fapolicyd-and-similar/Makefile
+++ b/selinux-policy/fapolicyd-and-similar/Makefile
@@ -64,6 +64,7 @@ $(METADATA): Makefile
@echo "Destructive: no" >> $(METADATA)
@echo "Releases: -RHEL4 -RHEL5 -RHEL6 -RHEL7" >> $(METADATA)
@echo "Bug: 1865818" >> $(METADATA) # RHEL-8
+ @echo "Bug: 1874491" >> $(METADATA) # Fedora 33
rhts-lint $(METADATA)
diff --git a/selinux-policy/fapolicyd-and-similar/runtest.sh b/selinux-policy/fapolicyd-and-similar/runtest.sh
index 3e69b01..f8ed470 100755
--- a/selinux-policy/fapolicyd-and-similar/runtest.sh
+++ b/selinux-policy/fapolicyd-and-similar/runtest.sh
@@ -63,6 +63,15 @@ rlJournalStart
rlSESearchRule "allow ${PROCESS_CONTEXT} net_conf_t : lnk_file { getattr read } [ ]"
rlPhaseEnd
+ rlPhaseStartTest "bz#1874491"
+ rlSEMatchPathCon "/usr/sbin/fapolicyd" ${FILE_CONTEXT}
+ rlSEMatchPathCon "/run/dbus/system_bus_socket" "system_dbusd_var_run_t"
+ rlSESearchRule "allow fapolicyd_t system_dbusd_var_run_t : sock_file { write } [ ]"
+ rlSESearchRule "allow fapolicyd_t system_dbusd_t : unix_stream_socket { connectto } [ ]"
+ rlSESearchRule "allow fapolicyd_t system_dbusd_t : dbus { send_msg } [ ]"
+ rlSESearchRule "allow system_dbusd_t fapolicyd_t : dbus { send_msg } [ ]"
+ rlPhaseEnd
+
rlPhaseStartTest "real scenario -- standalone service"
rlRun "echo ${ROOT_PASSWORD} | passwd --stdin root"
if ! rlSEDefined ${PROCESS_CONTEXT} ; then
reply other threads:[~2026-09-11 13:18 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=178913270100.1.7749888060309575103.tests-selinux-8c8d3ba91ee7@fedoraproject.org \
--to=mmalik@redhat.com \
--cc=git-commits@fedoraproject.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