All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Contribute blueman dbus mechanism policy from Fedora
Date: Mon, 09 Jan 2012 15:22:24 -0500	[thread overview]
Message-ID: <4F0B4C80.8090209@redhat.com> (raw)
In-Reply-To: <20120109200643.GA3416@siphos.be>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/09/2012 03:06 PM, Sven Vermeulen wrote:
> On Fri, Jan 06, 2012 at 12:18:31PM -0500, Daniel J Walsh wrote:
>> Policy from Fedora for blueman dbus mechanism.
> [...]
>> +######################################## +# +# Declarations +# 
>> + +type blueman_t; +type blueman_exec_t; 
>> +dbus_system_domain(blueman_t, blueman_exec_t)
> 
> Personally I'd put the dbus_system_domain() through an
> optional_policy() as we (Gentoo) don't have dbus as part of base.
> But I can imagine that systemd using distributions probably do have
> dbus as part of base ;-)
> 
> Looks okay.
> 
Since this is a dbus service, that really would not make much sense, I
would guess distributions that don't support dbus services would not
include these policies.
> Acked-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> 
> _______________________________________________ refpolicy mailing
> list refpolicy at oss.tresys.com 
> http://oss.tresys.com/mailman/listinfo/refpolicy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8LTIAACgkQrlYvE4MpobMrdwCeKDLnCkBrdE+EPqx4dfvIs17B
HDcAoI/jmi/kqVI9bnjuLij+hsakToHs
=rYcM
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-01-09 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 17:18 [refpolicy] Contribute blueman dbus mechanism policy from Fedora Daniel J Walsh
2012-01-09 20:06 ` Sven Vermeulen
2012-01-09 20:22   ` Daniel J Walsh [this message]
2012-01-09 21:10     ` Sven Vermeulen

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=4F0B4C80.8090209@redhat.com \
    --to=dwalsh@redhat.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.