David Herrmann 3723263f49 bus-proxy: never apply policy when sending signals ... Unlike dbus-daemon, the bus-proxy does not know the receiver of a broadcast (as the kernel has exclusive access on the bus connections). Hence, and "destination=" matches in dbus1 policies cannot be applied. But kdbus does not place any restrictions on *SENDING* broadcasts, anyway. The kernel never returns EPERM to KDBUS_CMD_SEND if KDBUS_MSG_SIGNAL is set. Instead, receiver policies are checked. Hence, stop checking sender policies for signals in bus-proxy and leave it up to the kernel. This fixes some network-manager bus-proxy issues where NM uses weird dst-based matches against interface-based matches. As we cannot perform dst-based matches, our bus-proxy cannot properly implement this policy.		2015-07-01 18:32:51 +02:00
..
bus-proxyd.c	turn kdbus support into a runtime option	2015-06-17 18:01:49 +02:00
bus-xml-policy.c	bus-proxy: ignore 'log' attributes in XML policy	2015-06-25 13:13:17 +02:00
bus-xml-policy.h	remove unused includes	2015-02-23 23:53:42 +01:00
driver.c	bus-proxy: fix GetConnectionSELinuxSecurityContext() return value	2015-05-21 21:24:55 +02:00
driver.h	bus-proxy: share policy between threads	2015-01-17 18:27:23 +01:00
Makefile	rename stdio-bridge to bus-proxyd	2013-11-29 22:12:59 +01:00
proxy.c	bus-proxy: never apply policy when sending signals	2015-07-01 18:32:51 +02:00
proxy.h	bus-proxy: complain only once about queue overflows	2015-03-11 13:57:38 +01:00
stdio-bridge.c	turn kdbus support into a runtime option	2015-06-17 18:01:49 +02:00
synthesize.c	bus-proxy: add support for "GetConnectionCredentials" method	2015-03-10 16:12:14 +01:00
synthesize.h	bus-proxy: add support for "GetConnectionCredentials" method	2015-03-10 16:12:14 +01:00
test-bus-xml-policy.c	remove unused includes	2015-02-23 23:53:42 +01:00