Fix dbus policy to allow signal send by default

to avoid unexpected denial on ALARM prefix users

Jan 01 21:46:26 localhost dbus[2521]: [system] Rejected send message, 2 matched rules;
type="signal", sender=":1.5" (uid=0 pid=2494 comm="/usr/sbin/actd ") interface="org.tizen.system.Booting"
member="BootingDone" error name="(unset)" requested_reply="0" destination="dpm.analytics" privilege="(n/a)"
(bus) rule(<deny send_path="/org/tizen/system" send_interface="org.tizen.system.Booting"
send_member="BootingDone" send_type="error" />)

Change-Id: I38aaf83bce28a3152522cec491fd2f89cdbfc984
Signed-off-by: Hyotaek Shim <hyotaek.shim@samsung.com>

diff --git a/alarm-service.conf.in b/alarm-service.conf.in
index 157e415..7ffdafd 100644 (file)
--- a/alarm-service.conf.in
+++ b/alarm-service.conf.in
@@ -16,7 +16,7 @@
                <deny send_destination="org.tizen.alarm.manager"/>
                <deny own_prefix="ALARM"/>
                <check own_prefix="ALARM" privilege="http://tizen.org/privilege/alarm.set"/>
-               <deny send_destination_prefix="ALARM" send_path="/org/tizen/alarm/client"/>
+               <deny send_destination_prefix="ALARM" send_path="/org/tizen/alarm/client" send_type="method_call"/>
                <deny send_destination_prefix="ALARM" send_path="/org/tizen/alarm/manager" send_interface="org.tizen.alarm.manager" send_member="alarm_expired" send_type="signal"/>
                <allow send_destination="org.tizen.alarm.manager" send_interface="org.freedesktop.DBus.Properties" send_member="GetAll"/>
                <allow send_destination="org.tizen.alarm.manager" send_interface="org.freedesktop.DBus.Properties" send_member="Get"/>