D-Bus Policy needs checking
smart-notifier builds one or more binary packages that contain D-Bus system
bus services. The following were detected:
The D-Bus policy needs checking!
It was discovered that the default policy of the D-Bus system bus was
not as was expected, due to a quirk of the language. In fact, whereas
the default policy was supposed to have been that messages would not be
allowed by default, the default was in fact that messages _were_
CVE-2008-4311 was issued, and a new release of D-Bus was updated to
correct the default policy to be deny-by-default.
It was quickly discovered that the policy files shipped by most services
no longer worked, and that many were (inadvertently, perhaps) relying on
the misconfiguration of the daemon.
A new version of D-Bus has been uploaded to jaunty co correct this.
Please read the following carefully to assist with updating the
The default policy of the D-Bus system bus is:
- Name ownership is DENIED by default.
- Method calls are DENIED by default.
- Replies to method calls, including errors, are PERMITTED by default.
- Signals are PERMITTED by default.
Therefore each service MUST, in its policy configuration:
- Permit an appropriate user to own the name it wishes to claim:
- Allow method calls to be made on objects it exports, for particular
users. This may be done in a number of different ways.
You may simply allow all method calls to your claimed name:
You may allow method calls to particular interfaces you export,
especially useful if you have privileged and non-privileged
*IMPORTANT* you MUST include send_destination on ALL allow or deny
tags. Omitting it is a SERIOUS bug!
This allows any service to receive method calls of the given
interface, not just your own service!
It also implicitly allows any service to receive method calls
with no interface specified, in case they match this interface!
Using the above means you are potentially allowing exploiting of
a different service. DO NOT DO IT!
This denies all services from receiving method calls of the
given interface, not just your own service! It also implicitly
denies all services from receiving method calls with no
interface specified. DO NOT DO IT!
- You must allow standard interfaces as well, such as Introspection and
- You should not normally allow receipt of any messages sent from your
interface, this is also the default.
(ie. remove any lines of the form <allow receive_*>)
- You do not normally need to deny any messages, this is the default.
(ie. remove any lines of the form <deny...>)
You should fully test the service with the new D-Bus after updating the
policy, you'll need to restart the bus daemon for that (it's probably
easier to reboot).
If messages are being denied, it will be logged in /var/log/auth.log as
Dec 19 14:17:53 space-ghost dbus: Rejected send message, 1 matched
member="(unset)" error name="(unset)" requested
_reply=0 destination=":1.18" (uid=0 pid=2806 comm="NetworkMa
Be aware that a denied message may still happen if you have other
invalid policy installed (such as those which don't qualify allow/deny
rules with the destination!). Take the opportunity to fix all you see.