From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v3] dbus: let session bus daemon manage user runtime dirs
Date: Wed, 24 May 2017 18:48:00 +0200 [thread overview]
Message-ID: <1495644480.13711.7.camel@trentalancia.com> (raw)
In-Reply-To: <20170524135934.GC1910@julius.enp8s0.d30>
Let the session dbus process manage user runtime directories (with
its own file type).
This is the third version (v3) of the patch, thanks to Dominick
Grift for revising the previous two versions and suggesting
improvements.
Signed-off-by: Guido Trentalancia <guido@trentalancia.com>
---
policy/modules/contrib/dbus.fc | 2 ++
policy/modules/contrib/dbus.te | 8 ++++++++
2 files changed, 10 insertions(+)
--- a/policy/modules/contrib/dbus.fc 2017-03-29 17:58:00.272386397 +0200
+++ b/policy/modules/contrib/dbus.fc 2017-05-24 18:41:36.105674966 +0200
@@ -4,6 +4,8 @@ HOME_DIR/\.dbus(/.*)? gen_context(sys
/run/dbus(/.*)? gen_context(system_u:object_r:system_dbusd_var_run_t,s0)
/run/messagebus\.pid -- gen_context(system_u:object_r:system_dbusd_var_run_t,s0)
+/run/user/%{USERID}/dbus-1(/.*)? gen_context(system_u:object_r:session_dbusd_runtime_t,s0)
+/run/user/%{USERID}/dbus-1/bus -s gen_context(system_u:object_r:session_dbusd_runtime_t,s0)
/usr/bin/dbus-daemon(-1)? -- gen_context(system_u:object_r:dbusd_exec_t,s0)
--- a/policy/modules/contrib/dbus.te 2017-04-26 17:47:20.555423022 +0200
+++ b/policy/modules/contrib/dbus.te 2017-05-24 18:43:56.536674392 +0200
@@ -47,6 +47,9 @@ type system_dbusd_var_run_t;
files_pid_file(system_dbusd_var_run_t)
init_daemon_pid_file(system_dbusd_var_run_t, dir, "dbus")
+type session_dbusd_runtime_t;
+files_pid_file(session_dbusd_runtime_t)
+
ifdef(`enable_mcs',`
init_ranged_system_domain(system_dbusd_t, dbusd_exec_t, s0 - mcs_systemhigh)
')
@@ -204,6 +207,11 @@ manage_dirs_pattern(session_bus_type, se
manage_files_pattern(session_bus_type, session_dbusd_tmp_t, session_dbusd_tmp_t)
files_tmp_filetrans(session_bus_type, session_dbusd_tmp_t, { dir file })
+manage_dirs_pattern(session_bus_type, session_dbusd_runtime_t, session_dbusd_runtime_t)
+manage_files_pattern(session_bus_type, session_dbusd_runtime_t, session_dbusd_runtime_t)
+manage_sock_files_pattern(session_bus_type, session_dbusd_runtime_t, session_dbusd_runtime_t)
+userdom_user_runtime_filetrans(session_bus_type, session_dbusd_runtime_t, { dir file sock_file })
+
kernel_read_system_state(session_bus_type)
kernel_read_kernel_sysctls(session_bus_type)
next prev parent reply other threads:[~2017-05-24 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 12:39 [refpolicy] [PATCH] dbus: let session bus daemon manage user runtime dirs Guido Trentalancia
2017-05-24 12:44 ` Dominick Grift
2017-05-24 13:25 ` Guido Trentalancia
2017-05-24 13:25 ` [refpolicy] [PATCH v2] " Guido Trentalancia
2017-05-24 13:59 ` Dominick Grift
2017-05-24 16:48 ` Guido Trentalancia [this message]
2017-05-24 16:56 ` [refpolicy] [PATCH v3] " Dominick Grift
2017-05-24 17:14 ` Guido Trentalancia
2017-05-24 17:19 ` Dominick Grift
2017-05-24 17:32 ` Guido Trentalancia
2017-05-24 17:44 ` [refpolicy] [PATCH v4] " Guido Trentalancia
2017-05-25 11:23 ` [refpolicy] [PATCH v5] " Guido Trentalancia
2017-05-26 0:56 ` Chris PeBenito
2017-05-24 23:19 ` [refpolicy] [PATCH v3] " Chris PeBenito
2017-05-25 5:57 ` Dominick Grift
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=1495644480.13711.7.camel@trentalancia.com \
--to=guido@trentalancia.com \
--cc=refpolicy@oss.tresys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.