<div dir="ltr"><p style="color: rgb(0, 0, 0);"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">Hi,</span></font></p>
<p style="color: rgb(0, 0, 0);"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">Our scenario is as follows.</span></font></p>
<p style="color: rgb(0, 0, 0);"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> </span></font></p>
<ol style="margin-top: 0in; color: rgb(0, 0, 0);" start="1" type="1"><li><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">We
have an application running on a Linux PC (server) and it
exports certain APIs for setting some parameters of the application.</span></font></li><li><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">The
user interface (GUI) for setting the options can run on the same m/c or on
a remote m/c. This user interface will be provided the server IP address
on startup.</span></font></li><li><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">The
parameters selected by the user will be set using the interfaces exported
by the server application.</span></font></li><li><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">No
authentication is required as of now.</span></font></li></ol>
<p style="color: rgb(0, 0, 0);"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> </span></font></p>
<p style="color: rgb(0, 0, 0);"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">The same thing could be achieved using a
proprietary kind of communication. We would like to know whether DBUS will be a
right option for that.</span></font></p>
<p style="color: rgb(0, 0, 0);"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;"> </span></font></p>
<p style="color: rgb(0, 0, 0);"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;">Regards</span></font></p>Remya<br><br><br><br><br><br>Hi,<br>
<br>
You have to figure out authentication, see for example some of these threads:<br>
<a href="http://lists.freedesktop.org/archives/dbus/2007-June/008066.html" target="_blank">http://lists.freedesktop.org/archives/dbus/2007-June/008066.html</a><br>
<a href="http://lists.freedesktop.org/archives/dbus/2008-February/009331.html" target="_blank">http://lists.freedesktop.org/archives/dbus/2008-February/009331.html</a><br>
<br>
The only known-working uses of TCP with dbus right now are:<br>
* to share the session bus when a user is logged into two machines<br>
sharing a home directory via a networked filesystem<br>
* to write a custom DBusServer (NOT a dbus-daemon) that accepts<br>
anonymous connections<br>
<br>
Other uses are possibly trivial to implement, but they are not<br>
implemented. So you would have to look into adding more features to<br>
dbus to support them.<br>
<br>
If you explain what you are trying to do on a higher level someone may<br>
have more advice about what sort of auth you could be using.<br>
<br>
Always remember this point made in the dbus spec:<br>
<br>
D-Bus is designed for two specific use cases:<br>
<br>
* A "system bus" for notifications from the system to user<br>
sessions, and to allow the system to request input from user sessions.<br>
* A "session bus" used to implement desktop environments such as<br>
GNOME and KDE.<br>
<br>
D-Bus is not intended to be a generic IPC system for any possible<br>
application, and intentionally omits many features found in other IPC<br>
systems for this reason.<br>
D-Bus may turn out to be useful in unanticipated applications, but<br>
future versions of this spec and the reference implementation probably<br>
will not incorporate features that interfere with the core use cases.<br>
<font color="#888888"><br>
Havoc</font></div>