a87d2ed1ce1e7d5810bb2a5f8ebfd3719543d109 |
|
31-Jul-2015 |
David Herrmann <dh.herrmann@gmail.com> |
bus-proxy: don't filter directed signals
NameAcquired and NameLost are directed signals. Never ever filter them on
dbus1. On dbus1, filters *exclusively* apply to broadcasts! Hence, we
must always forward directed signals unconditionally! |
e23bc0e7cac8ba79f4e14ab98ecd68c79cc87aab |
|
16-Jul-2015 |
David Herrmann <dh.herrmann@gmail.com> |
bus-proxy: never pass on unmatched broadcasts
The lovely libvirtd goes into crazy mode if it receives broadcasts that
it didn't subscribe to. With bus-proxyd, this might happen in 2 cases:
1) The kernel passes us an unmatched signal due to a false-positive
bloom-match.
2) We generate NameOwnerChanged/NameAcquired/NameLost locally even
though the peer didn't subscribe to it.
dbus-daemon is reliable in what signals it passes on. So make sure we
follow that style. Never ever send a signal to a local peer if it doesn't
match an installed filter of that peer. |
52fa7a3af1322aa716e5afc08b60ff2e9e13c022 |
|
10-Mar-2015 |
Lukasz Skalski <l.skalski@samsung.com> |
bus-proxy: add support for "GetConnectionCredentials" method
GetConnectionCredentials method was added to dbus-1 specification
more than one year ago. This method should return "[...] as many
credentials as possible for the process connected to the server",
but at this moment only "UnixUserID", "LinuxSecurityLabel" and
"ProcessID" are defined by the specification. We should add support
for next credentials after extending dbus-1 spec. |
5f6cb091278906423f8b7e70c40131db7269916a |
|
13-Feb-2015 |
Lennart Poettering <lennart@poettering.net> |
bus-proxy: whenever we cannot forward a message, report this back to caller, but don't exit
Errors like EPERM from the kernel should certainly not be reason to
exit. Let's try to be defensive here, and try to continue on most send
errors, but possibly tell the sender about it. |