Posted May 22, 2012 14:31 UTC (Tue) by nix (subscriber, #2304)
Parent article: Announcing printerd
I'd not mind this increasing emphasis on D-Bus if there was a sane way to allow D-Bus session bus connections to be tunnelled over the network. Unfortunately it seems we currently have two possibilities:
- local AF_UNIX sockets with randomly-assigned names in a fixed directory, with a name exported via an environment variable (the default). Local system only, you're on a remote system? Sucks to be you.
- remote IP connection, not really per-session as there is no automatic port assignment, SSH forwarding or anything else. i.e. you can say
in session.conf, but what you cannot say is 'assign a port automatically, and export it in an environment variable', let alone 'get SSH to forward-and-proxy a connection to the dbus session bus', which would allow a secure session bus across the network. This is not rocket science -- it's the preferred way of handling X connections -- but as far as I can see D-Bus is incapable of it. Am I wrong?
(Obviously doing this securely would involve -- fairly trivial -- changes to OpenSSH as well.)