From: Martin Orr <martin@martinorr.name>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: [refpolicy] dbus/lvm read domain state
Date: Sun, 15 Mar 2009 16:09:19 +0000 [thread overview]
Message-ID: <49BD282F.2050609@martinorr.name> (raw)
Both dbus and lvm want to read other processes' command lines.
In the case of dbus, this is for use in log messages, which is probably useful.
In the case of lvm, it is just to print in a warning if the parent process
leaks fds to it, which I doubt is important enough to allow.
Index: policy/modules/services/dbus.te
===================================================================
--- policy/modules/services/dbus.te.orig
+++ policy/modules/services/dbus.te
@@ -94,6 +94,7 @@
corecmd_read_bin_sockets(system_dbusd_t)
corecmd_exec_bin(system_dbusd_t)
+domain_read_all_domains_state(system_dbusd_t)
domain_use_interactive_fds(system_dbusd_t)
files_read_etc_files(system_dbusd_t)
Index: policy/modules/system/lvm.te
===================================================================
--- policy/modules/system/lvm.te.orig
+++ policy/modules/system/lvm.te
@@ -243,6 +243,7 @@
corecmd_exec_bin(lvm_t)
corecmd_exec_shell(lvm_t)
+domain_dontaudit_read_all_domains_state(lvm_t)
domain_use_interactive_fds(lvm_t)
files_read_etc_files(lvm_t)
--
Martin Orr
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2009-03-15 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 16:09 Martin Orr [this message]
2009-03-15 23:23 ` [refpolicy] dbus/lvm read domain state Russell Coker
2009-03-31 14:51 ` Martin Orr
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=49BD282F.2050609@martinorr.name \
--to=martin@martinorr.name \
--cc=cpebenito@tresys.com \
--cc=selinux@tycho.nsa.gov \
/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.