From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: missing file context for system-tools-backends (gnome)
Date: Wed, 20 Jun 2012 23:03:01 +0200 [thread overview]
Message-ID: <1340226181.23287.2.camel@vortex> (raw)
I think the following file context is still missing in current reference
policy for an optional Gnome package (that shouldn't need its own
policy):
Add the generic binary executable label to the script from System Tools
Backends.
Signed-off-by: Guido Trentalancia <guido@trentalancia.com>
---
policy/modules/contrib/gnome.fc | 2 ++
1 file changed, 2 insertions(+)
--- refpolicy-04062012/policy/modules/contrib/gnome.fc 2011-09-09 18:29:23.571610910 +0200
+++ refpolicy-04062012-system-tools-backends/policy/modules/contrib/gnome.fc 2012-06-20 22:41:01.448465819 +0200
@@ -7,3 +7,5 @@ HOME_DIR/\.gnome2(/.*)? gen_context(sys
/tmp/gconfd-USER/.* -- gen_context(system_u:object_r:gconf_tmp_t,s0)
/usr/libexec/gconfd-2 -- gen_context(system_u:object_r:gconfd_exec_t,s0)
+
+/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -- gen_context(system_u:object_r:bin_t,s0)
next reply other threads:[~2012-06-20 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 21:03 Guido Trentalancia [this message]
2012-06-21 8:41 ` [refpolicy] [PATCH]: missing file context for system-tools-backends (gnome) Dominick Grift
2012-06-21 17:38 ` Guido Trentalancia
2012-06-21 17:58 ` Dominick Grift
2012-06-21 18:06 ` Dominick Grift
2012-06-21 18:41 ` [refpolicy] [PATCH v2]: " Guido Trentalancia
2012-06-21 18:53 ` Daniel J Walsh
2012-06-21 18:27 ` [refpolicy] [PATCH]: " Guido Trentalancia
2012-06-23 8:59 ` Guido Trentalancia
2012-06-23 9:12 ` Dominick Grift
2012-06-23 9:52 ` Guido Trentalancia
2012-06-23 10:19 ` Dominick Grift
2012-06-24 1:14 ` Guido Trentalancia
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=1340226181.23287.2.camel@vortex \
--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.