Good evening,
I've got a problem while trying to run DBus Daemon as dbus user on port 2426.
In short - when I'm trying to connect to it, I'm getting empty response although nmap shows the port as open.
When I start DBus Daemon as root when it starts replying over port 2426.
What's wrong?
Config(s):
- dbus.conf
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<listen>tcp:host=0.0.0.0,port=2426</listen>
<!-- Only root or user avahi can own the Avahi service -->
<policy user="avahi">
<allow own="org.freedesktop.Avahi"/>
</policy>
<policy user="root">
<allow own="org.freedesktop.Avahi"/>
</policy>
<policy group="dbus">
<allow own="org.freedesktop.DBus"/>
</policy>
<policy group="network">
<allow own="org.freedesktop.DBus"/>
</policy>
<!-- Allow anyone to invoke methods on Avahi server, except SetHostName -->
<policy context="default">
<allow send_destination="org.freedesktop.Avahi"/>
<allow receive_sender="org.freedesktop.Avahi"/>
<allow send_destination="org.freedesktop.DBus"/>
<allow receive_sender="org.freedesktop.DBus"/>
</policy>
<!-- Allow everything, including access to SetHostName to users of the group "network" -->
<policy group="network">
<allow send_destination="org.freedesktop.Avahi"/>
<allow receive_sender="org.freedesktop.Avahi"/>
<allow send_destination="org.freedesktop.DBus"/>
<allow receive_sender="org.freedesktop.DBus"/>
</policy>
<policy group="dbus">
<allow send_destination="org.freedesktop.DBus"/>
<allow receive_sender="org.freedesktop.DBus"/>
</policy>
<policy user="root">
<allow send_destination="org.freedesktop.Avahi"/>
<allow receive_sender="org.freedesktop.Avahi"/>
</policy>
</busconfig>
- DBus Daemon launch command:
sudo -u dbus dbus-daemon --config-file /path/to/dbus.conf --nofork --syslog --print-address
- DBus Test Tool response:
~> DBUS_SESSION_BUS_ADDRESS="tcp:host=127.0.0.1,port=2426" dbus-test-tool echo
Failed to connect to bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
There's nothing inside syslog log files even if dbus is in both network & log group.