Issues while using DBUS over TCP

Havoc Pennington hp at
Sun Jul 27 22:43:29 PDT 2008


You have to figure out authentication, see for example some of these threads:

The only known-working uses of TCP with dbus right now are:
* to share the session bus when a user is logged into two machines
sharing a home directory via a networked filesystem
* to write a custom DBusServer (NOT a dbus-daemon) that accepts
anonymous connections

Other uses are possibly trivial to implement, but they are not
implemented. So you would have to look into adding more features to
dbus to support them.

If you explain what you are trying to do on a higher level someone may
have more advice about what sort of auth you could be using.

Always remember this point made in the dbus spec:

   D-Bus is designed for two specific use cases:

    * A "system bus" for notifications from the system to user
sessions, and to allow the system to request input from user sessions.
    * A "session bus" used to implement desktop environments such as

   D-Bus is not intended to be a generic IPC system for any possible
application, and intentionally omits many features found in other IPC
systems for this reason.
   D-Bus may turn out to be useful in unanticipated applications, but
future versions of this spec and the reference implementation probably
will not incorporate features that interfere with the core use cases.


More information about the dbus mailing list