On 2025-01-21 11:05, Erik Slagter wrote:
Duly noted!
But as I already wrote to Lennart, this is for a home environment.
Besides my hobby as a programmer, in daily life I am a network admin. So
I am quite aware of all the dangers lurking. There is a reason I have
quite a bunch of vlans, vrfs and ssids. So believe me when I say there
will be no other trusted or rogue client able to connect to this tcp
socket than the one I allow. There is only the user level authentication
issue. But that's actually no real issue as there is only one "user"
user active in my home network (other than root etc.), me. No publicly
accessible network outlets or switchports, no ssids that allow unknown
clients etc...
So now we have wavered all responsibilities. Is it possible or is it not
possible? Dbus-broker listening on tcp? If it's not possible, my
question is answered and I can go move on.
...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.
