There are plans to get D-Bus communication working also in
situations where the two programs are not on the same computer
and thus cannot use the default unix domain sockets.
Possibilities include TCP/IP, SSH forwarding the bus daemon, a
proxy daemon, or D-Bus over X. TCP/IP and SSH forwarding could
in theory work without further programming. Most remote
scenarios would require authentication of end points and
encryption of messages on the wire though. A simple use case is
running a remote application that wants to communicate with the
local session bus. Another interesting setup is running an X
session and the session bus remotely on a server machine, but
allow the applications to contact the system bus running locally
on a thin client. The TCP/IP transport isn't tested in use and
it has the problems of access control, lack of encryption, and
inability to go through firewalls and NAT. SSH doesn't support
forwarding of unix domain sockets. Even if it did, the methods
that return unix user and unix process wou