From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [ cgroups revisited 3/4] Allow login users to list both cgroup as well as cgroupfs dirs.
Date: Wed, 28 Apr 2010 12:02:14 +0200 [thread overview]
Message-ID: <20100428100211.GA6512@localhost.localdomain> (raw)
This seems needed but i have not figured out completely why.
I know some atlleast that some gnome wants it but i am not sure as to whether text login users need it.
I do not see a big problem with allowing this myself though.
In some cases regular users can be allowed to edit cgroupfs files, and in that case they will need
this access as well.
Signed-off-by: Dominick Grift <domg472@gmail.com>
---
:100644 100644 990063c... 97af220... M policy/modules/system/userdomain.if
policy/modules/system/userdomain.if | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/policy/modules/system/userdomain.if b/policy/modules/system/userdomain.if
index 990063c..97af220 100644
--- a/policy/modules/system/userdomain.if
+++ b/policy/modules/system/userdomain.if
@@ -753,6 +753,7 @@ template(`userdom_login_user_template', `
fs_getattr_all_fs($1_t)
fs_getattr_all_dirs($1_t)
fs_search_auto_mountpoints($1_t)
+ fs_list_cgroupfs_dirs($1_t)
fs_list_inotifyfs($1_t)
fs_rw_anon_inodefs_files($1_t)
@@ -779,6 +780,10 @@ template(`userdom_login_user_template', `
seutil_read_config($1_t)
optional_policy(`
+ cgroup_list_cgroup_dirs($1_t)
+ ')
+
+ optional_policy(`
cups_read_config($1_t)
cups_stream_connect($1_t)
cups_stream_connect_ptal($1_t)
--
1.7.0.1
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20100428/bd06de6a/attachment.bin
reply other threads:[~2010-04-28 10:02 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=20100428100211.GA6512@localhost.localdomain \
--to=domg472@gmail.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.