On 21-01-2025 17:06, Mantas Mikulėnas wrote:
...Do note though that even though dbus-broker was caused by systemd, it
isn't really *part of* systemd, and I don't know if any of its
developers even read the systemd mailing list anymore. So if you never
get a definite answer, that would be why.
Interesting!
I was under the impression that dbus-broker was developed especially for
systemd, also it has a tight integration with systemd, so that's why I
came here. But maybe that assumption is wrong.
For the moment I know enough though.
- dbus-broker does not support TCP sockets (dbus-broker-launch actively
checks for this and there is no way to workaround this)
- dbus-daemon has something weird (bug?) that prevents it from being
used remotely, even though it can listen on a TCP socket. From what I
read from some version up they did "something" to the authentication so
"anonymous" doesn't work anymore and the "external" auth doesn't play at
all with at least busctl (so probably all dbus clients).
So the only way that will work is tunneling over socat or stunnel.
