How to debug dbus access issues?

[tomw]

Thanks, that's exactly what I did (even taking the avahi example :-)
What I don't understand is that a method call from the specified user
using dbus-send to an object exported by a Python script (and and
the .conf files in system.d) works whereas it does not work calling the
same method from another Python script.


On Di, 2011-08-23 at 12:25 +0100, Simon McVittie wrote:
> On Tue, 23 Aug 2011 at 12:43:12 +0200, tomw wrote:
> > Python and SessionBus   - works
> 
> The session bus has a default-allow security policy, because it isn't a
> security boundary (all applications in the login session are assumed to be
> equally-privileged).
> 
> > Python and SystemBus    - does not work:
> 
> The system bus has a default-deny security policy. Put a .conf file in
> /etc/dbus-1/system.d that allows what you want to allow; as an example that is
> simple enough to understand, but not *too* simple, I usually recommend looking
> at the policy for Avahi.
> 
> The format of the access control policy configuration language is defined in
> the dbus-daemon man page.
> 
>     S
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus