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

[Simon McVittie]

On Wed, 07 Jan 2009 at 15:26:31 -0500, Colin Walters wrote:
> On Wed, Jan 7, 2009 at 3:09 PM, Simon McVittie
> <simon.mcvittie at collabora.co.uk> wrote:
> >
> > As far as I can tell, BlueZ agents work like this:
> 
> Urf.  Can we just change this to use signals?  Signals can be sent to
> a particular destination only (I'm pretty sure).

As a long-term solution, that'd probably be a good thing to suggest (I've
avoided cross-posting to BlueZ upstream, until we have a consistent
recommendation to give them!)

As a solution for the current release of BlueZ, assuming that rethinking
the Agent API completely is not an option, does the proposed policy at
<http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=59;filename=bluetooth.conf;att=1;bug=510644>
need to be vetoed? It seems to me to be non-ideal, but the best we can get
right now; but I still don't fully understand the D-Bus policy language (I'm
not convinced anyone does...) so I could be wrong.

(It is intentional that the netdev group always have privileges equal to an
at_console user; that particular change is an odd Debianism caused by
ConsoleKit/pam_console/etc. not being a hard dependency.)

Thanks,
    Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 155 bytes
Desc: Digital signature
Url : http://lists.freedesktop.org/archives/dbus/attachments/20090107/507b2cc5/attachment.pgp