All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: missing file context for system-tools-backends (gnome)
Date: Sat, 23 Jun 2012 10:59:55 +0200	[thread overview]
Message-ID: <1340441995.2934.5.camel@vortex> (raw)
In-Reply-To: <1340301537.9690.45.camel@x220.mydomain.internal>

On Thu, 2012-06-21 at 19:58 +0200, Dominick Grift wrote:
> On Thu, 2012-06-21 at 19:38 +0200, Guido Trentalancia wrote:
> > Hello Dominick.

[cut]

> Looking at the fedora policy seems it only needs:
> 
> # needed for system-tools-backends
> corecmd_exec_shell(system_dbusd_t)

And by the way, since you were asking, comecmd_exec_bin is needed when
the backends are executed, for example, by gnome-system-tools (since the
script had been labelled as a generic binary executable to avoid
creating a new module built for the purpose).

Not everybody might want system_dbusd_t to execute binaries, so that's
the reason for the boolean.

Regards,

Guido

  parent reply	other threads:[~2012-06-23  8:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 21:03 [refpolicy] [PATCH]: missing file context for system-tools-backends (gnome) Guido Trentalancia
2012-06-21  8:41 ` 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 [this message]
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=1340441995.2934.5.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.