Am Dienstag 02 Januar 2007 18:52 schrieb Marcel Holtmann:
> > > > Beside that, running the dbus command suggested in this bug report
> > > > works, too. It should be noted, though, that you have to be root.
> > >
> > > No. You have to be console user (or root).
> >
> > I cite from dbus policy that I somehow just don't get (too many english
> > words are different between dbus-send manpage, policy snippet and
> > dbus-api.txt :-O
> >
> > The policy for bluez-utils:
> >   <policy user="root">
> >     <allow own="org.bluez"/>
> >   </policy>
> >
> >   <policy at_console="true">
> >     <allow send_destination="org.bluez.Adapter"/>
> >     <allow receive_sender="org.bluez.Adapter"/>
> >
> >     <allow send_path="/org/bluez/Adapter"/>
> >
> >     <allow send_destination="org.bluez.Manager"/>
> >     <allow receive_sender="org.bluez.Manager"/>
> >
> >     <allow send_path="/org/bluez/Manager"/>
> >
> >     <allow send_destination="org.bluez.Security"/>
> >     <allow receive_sender="org.bluez.Security"/>
> >   </policy>
>
> this is a bluez-utils-2.x config file and simply outdated. Check the
> source code for the latest one.

No, this (well above is only what inside the <busconfig> thing) is what's in 
Debian's bluez-utils-3.7 source package under hcid/bluez-hcid.conf (and also 
in the orig.tar.gz).
Even -3.8 from bluez.sf.net contains the same one as hcid/bluetooth.conf.
AFAIK, this _is_ the latest one.

HS


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to