All of lore.kernel.org
 help / color / mirror / Atom feed
From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] refpolicy-2.20101213 (mcs) and dbus messages
Date: Fri, 14 Jan 2011 10:34:13 +0100	[thread overview]
Message-ID: <4D301895.3050409@gmail.com> (raw)
In-Reply-To: <1294960535.3100.14.camel@tesla.lan>

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

On 01/14/2011 12:15 AM, Guido Trentalancia wrote:
> Hi Dominick !
> 
> On Thu, 13/01/2011 at 22.43 +0100, Dominick Grift wrote:
>>> But in general for USER_AVCs there is nothing like audit2allow that can
>>> be used to ease the job ?
>>
>> audit2allow can also be used for these dbus AVC' s sure. But if you want
>> this stuff upstreamed then you will have to play by upstreams rules
>> (style rules)
> 
> No, apparently audit2allow doesn't do the job for USER_AVCs.

Strange, in that case i guess you will have to translate it manually.

1.

AVC denial:

> > denied  { send_msg } for msgtype=method_call
> > interface=org.freedesktop.Hal.Manager member=FindDeviceByCapability
> > dest=org.freedesktop.Hal spid=2928 tpid=2314
> > scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
> > tcontext=system_u:system_r:hald_t:s0 tclass=dbus :
> > exe="/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'

Raw policy:

allow xdm_t hald_t:dbus send_msg;

Possible macro/interface:

hal_dbus_chat(xdm_t)

2.

> > denied  { send_msg } for msgtype=signal
> > interface=org.freedesktop.PolicyKit1.Authority member=Changed
> > dest=org.freedesktop.DBus spid=2613 tpid=2546
> > scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023
> > tcontext=system_u:system_r:consolekit_t:s0-s0:c0.c1023 tclass=dbus :
> > exe="/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
> >

Raw policy:

allow system_dbusd_t consolekit_t:dbus send_msg;

Possible macro/interface:

consolekit_dbus_chat(system_dbusd_t)

3.

> > denied  { send_msg } for msgtype=method_call
> > interface=org.freedesktop.DBus.Properties member=GetAll
> > dest=org.freedesktop.UDisks spid=3567 tpid=3569
> > scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
> > tcontext=system_u:system_r:devicekit_disk_t:s0-s0:c0.c1023 tclass=dbus :
> > exe="/bin/dbus-daemon" sauid=81 hostname=? addr=?
> > terminal=?'

Raw policy:

allow xdm_t devicekit_disk_t:dbus send_msg;

Possible macro/interface:

devicekit_dbus_chat_disk(xdm_t)


But this is only the start, You will probably encounter many more policy
issues. You will need to be able to analyse them and resolve issues
accordingly.

> Regards,
> 
> Guido
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0wGJUACgkQMlxVo39jgT/JeQCeOOJaD6xfHAC8okGnjE+qvNf+
Qi4An0KoDfyODqivlo/dFVkZ3pqLyQXw
=cmPo
-----END PGP SIGNATURE-----

  reply	other threads:[~2011-01-14  9:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 21:32 [refpolicy] refpolicy-2.20101213 (mcs) and dbus messages Guido Trentalancia
2011-01-13  9:19 ` Dominick Grift
2011-01-13 12:25   ` Guido Trentalancia
2011-01-13 12:34     ` Dominick Grift
     [not found]       ` <1294931759.3153.25.camel@tesla.lan>
2011-01-13 15:38         ` Dominick Grift
2011-01-13 19:24           ` Guido Trentalancia
2011-01-13 19:57             ` Dominick Grift
2011-01-13 21:37               ` Guido Trentalancia
2011-01-13 21:43                 ` Dominick Grift
2011-01-13 23:15                   ` Guido Trentalancia
2011-01-14  9:34                     ` Dominick Grift [this message]
2011-01-14 14:27                       ` Guido Trentalancia
2011-01-14 14:36                         ` Dominick Grift
2011-01-14 14:55                           ` Guido Trentalancia
2011-01-15 15:06                       ` Guido Trentalancia
  -- strict thread matches above, loose matches on Subject: below --
2011-01-13 15:21 Guido Trentalancia
2011-01-13 15:45 ` Dominick Grift
2011-01-13 19:49   ` Guido Trentalancia
2011-01-13 18:51     ` Dominick Grift

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=4D301895.3050409@gmail.com \
    --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.