From: sven.vermeulen@siphos.be (Sven Vermeulen) Date: Wed, 3 Oct 2012 23:54:22 +0200 Subject: [refpolicy] [PATCH] Changes to the dbus policy and its dependencies Message-ID: To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com Recently, the dbus policy has seen some changes. At least one of them makes an interface incompatible with its earlier declaration. dbus_session_bus_client() previously took its argument as being a domain ($1) and now takes the argument to create its own domain ($1_dbusd_t). As a result, modules that used to do something like "dbus_session_bus_client(chromium_t)" are now broken. I'm wondering, how are we supposed to work with these interfaces now? Do we need to declare the subtype ourselves (I don't think the idea is to use the dbus_role_template for non-user domains, but it seems that this is the only interface that creates the specific type)?