Return-Path: Message-ID: From: Claudio Takahasi To: bluez-devel@lists.sourceforge.net Subject: Re: [Bluez-devel] hcid D-Bus patch In-Reply-To: <1127644396.6362.6.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1348_21614191.1127735947095" References: <1127292701.495.11.camel@localhost.localdomain> <1127398647.5344.24.camel@blade> <1127411650.12287.15.camel@blade> <1127644396.6362.6.camel@localhost.localdomain> Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 26 Sep 2005 08:59:07 -0300 ------=_Part_1348_21614191.1127735947095 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Marcel, Define clear object paths and interfaces will make easier define rules in the D-Bus configuration file. In this file it's possible specify the permissions for send and receive messages based on the interfaces, paths an= d users/groups. Based on your comment I suggested the paths and interfaces. Defining this structure it's possible allow only the "root" or a "bluez manager" user/group change the adapter settings. SERVICE BUS NAME: org.bluez <=3D=3D=3D=3D=3D=3D=3D Device =3D=3D=3D=3D=3D=3D> description: device specific configuration services. eg: (#1)display local devices, inqmode, inqtype, up, down, reset, auth, noauth, encrypt, ... object path: /org/bluez/Device interface: /org/bluez/Device <=3D=3D=3D=3D=3D=3D=3D Manager =3D=3D=3D=3D=3D=3D> description: connection services. eg: inquiry, remote name, info, master/slave role switch, active connecions and profile specific tasks. Multiple local adapters scenario will be considered. The default object pat= h and the adapter specific paths will provide the same services. /***** HCI ******/ default object path:/org/bluez/Manager/hci (will use the default device in the kernel) object path: /org/bluez/Manager/hci0/hci object path: /org/bluez/Manager/hci1/hci interface: org.bluez.Manager.hci /***** SDP ******/ default object path:/org/bluez/Manager/sdp object path: /org/bluez/Manager/hci0/sdp object path: /org/bluez/Manager/hci1/sdp interface: org.bluez.Manager.sdp /***** PAN ******/ default object path:/org/bluez/Manager/pan object path: /org/bluez/Manager/hci0/pan object path: /org/bluez/Manager/hci1/pan interface: org.bluez.Manager.pan /***** RFCOMM ******/ default object path:/org/bluez/Manager/rfcomm object path: /org/bluez/Manager/hci0/rfcomm object path: /org/bluez/Manager/hci1/rfcomm interface: org.bluez.Manager.rfcomm ... (#1) Probably the display local devices should be moved to other path due the permissions that I comment before. User applications should be able lis= t the local adapters to use in the pan, rfcomm, sdp ... For me, your suggestion or my last suggestion are fine, both can address th= e permissions. You have the decision in your hands! :) Regards, Claudio On 9/25/05, Marcel Holtmann wrote: > > Hi Claudio, > > > Sorry, but the last patch(hcid_dbus_0007.patch) was not > > based on the latest CVS version. > > I realized that yesterday, but I am in Prague now for the UnPlugFest and > haven't had Internet access for two days. The patch looks good and I > think we now have a nice and clean base to start with. However there are > some names I like to change. For example using org.bluez.Device for all > device specific configuration, like name changes. And org.bluez.Manager > for Inquiry stuff etc. Do you think that makes sense? > > Regards > > Marcel > > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your ver= y > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Bluez-devel mailing list > Bluez-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bluez-devel > ------=_Part_1348_21614191.1127735947095 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Marcel,

Define clear object paths and interfaces will make easier define rules in the D-Bus configuration file. In this file it's possible specify the permissions for send and receive messages based on the interfaces, paths and users/groups.

Based on your comment I suggested the paths and interfaces. Defining this structure it's possible allow only the "root" or a "blu= ez manager" user/group change the adapter settings.


SERVICE BUS NAME: org.bluez

<=3D=3D=3D=3D=3D=3D=3D Device =3D=3D=3D=3D=3D=3D>
description: device specific configuration services. eg: (#1)display local devices, inqmode, inqtype, up, down, reset, auth, noauth, encrypt, ...

object path: /org/bluez/Device
interface: /org/bluez/Device

<=3D=3D=3D=3D=3D=3D=3D Manager =3D=3D=3D=3D=3D=3D>
description: connection services. eg: inquiry, remote name, info, master/slave role switch, active connecions and profile specific tasks.
Multiple local adapters scenario will be considered. The default object path and the adapter specific paths will provide the same services.

/***** HCI ******/
default object path:/org/bluez/Manager/hci (will use the default device in = the kernel)
object path: /org/bluez/Manager/hci0/hci
object path: /org/bluez/Manager/hci1/hci
interface: org.bluez.Manager.hci

/***** SDP ******/
default object path:/org/bluez/Manager/sdp
object path: /org/bluez/Manager/hci0/sdp
object path: /org/bluez/Manager/hci1/sdp
interface: org.bluez.Manager.sdp

/***** PAN ******/
default object path:/org/bluez/Manager/pan
object path: /org/bluez/Manager/hci0/pan
object path: /org/bluez/Manager/hci1/pan
interface: org.bluez.Manager.pan

/***** RFCOMM ******/
default object path:/org/bluez/Manager/rfcomm
object path: /org/bluez/Manager/hci0/rfcomm
object path: /org/bluez/Manager/hci1/rfcomm
interface: org.bluez.Manager.rfcomm

...
(#1) Probably the display local devices should be moved to other path due the permissions that I comment before. User  applications should be able list the local adapters to use in the pan, rfcomm, sdp ...


For me, your suggestion or my last suggestion are fine, both can address the permissions. You have the decision in your hands! :)


Regards,
Claudio

On 9/25/05, Marcel Holtmann <marcel@holtmann.org> wrote:
Hi Claudio,

> Sorry, but the last patch(hcid_dbus_0007.patch) was= not
> based on the latest CVS version.

I realized that yester= day, but I am in Prague now for the UnPlugFest and
haven't had Internet = access for two days. The patch looks good and I
think we now have a nice and clean base to start with. However there ar= e
some names I like to change. For example using org.bluez.Device for al= l
device specific configuration, like name changes. And org.bluez.Manage= r
for Inquiry stuff etc. Do you think that makes sense?

Regards
Marcel




--------------------------------------------= -----------
SF.Net email is sponsored by:
Tame your development chall= enges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or y= our very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/= lists/listinfo/bluez-devel

------=_Part_1348_21614191.1127735947095-- ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel