[Pkg-bluetooth-maintainers] Bug#510644: bluetooth.conf needs alterations for new D-Bus

[Marcel Holtmann]

Hi Colin,

> > As far as I can tell, BlueZ agents work like this:
> >
> > * the agent (a UI process run by a user) calls a method on the hci daemon (run
> >  by root) and passes in its unique name and its (arbitrary) object path
> > * later, the hci daemon calls a method on the agent
> >
> > so the only thing that can be relied on is that when the hci daemon calls
> > the method, it's on the org.bluez.Agent interface!
> 
> Urf.  Can we just change this to use signals?  Signals can be sent to
> a particular destination only (I'm pretty sure).

that is exactly how it works and we can't use signal. Even directed
signal are not working since the method call into the agent has to
return the result or an error.

What problem do you guys actually have with this? The agent inside
bluez-gnome is verifying that the method comes from the daemon it
registers its agent with and thus there is not even a security issue
here with trying to send arbitrary method calls to the UI.

Regards

Marcel