On Fri, 12 Dec 2014 at 23:25:37 +0100, [email protected] wrote:
> Further more, where can dnsmasq find this "uk.org.thekelleys.dnsmasq"
> configuration string?
It is not configuration, it is part of its API. D-Bus services are
identified by a well-known bus name (service name), an interface and
an object path, all of which are conventionally the reversed domain name
of the designer of the software. This has nothing to do with the domain
names being resolved or advertised by dnsmasq itself.
It's the same principle as the reversed domain names in Java package names
(e.g. org.apache.tomcat.InstanceManager is part of apache.org's Tomcat
package) and is done for very similar reasons.
> I configured dnsmasq on debian jessie.
> When starting dnsmasq, I receive:
> Erreur DBus : Connection ":1.57" is not allowed to own the service
> "uk.org.thekelleys.dnsmasq" due to security policies in the configuration file
The D-Bus system bus is a security boundary between users and is used
for trusted system services, so it has a deny-by-default policy.
In particular, to avoid unprivileged users impersonating system services,
a service cannot own a well-known bus name unless it is specifically
allowed to do so.
You should have a file /etc/dbus-1/system.d/dnsmasq.conf which
configures the system dbus-daemon to allow either root or dnsmasq to own
the name uk.org.thekelleys.dnsmasq; it's part of dnsmasq-base.
Please reinstall dnsmasq-base if necessary.
S
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
