Hi Marcel,<br>
<br>
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.<br>
<br>
Based on your comment I suggested the paths and interfaces. Defining
this structure it's possible allow only the &quot;root&quot; or a &quot;bluez manager&quot;
user/group change the adapter settings.<br>
<br>
<br>
SERVICE BUS NAME: org.bluez<br>
<br>
&lt;======= Device ======&gt;<br>
description: device specific configuration services. eg: (#1)display
local devices, inqmode, inqtype, up, down, reset, auth, noauth,
encrypt, ...<br>
<br>
object path: /org/bluez/Device<br>
interface: /org/bluez/Device<br>
<br>
&lt;======= Manager ======&gt;<br>
description: connection services. eg: inquiry, remote name, info,
master/slave role switch, active connecions and profile specific tasks.<br>
Multiple local adapters scenario will be considered. The default object
path and the adapter specific paths will provide the same services.<br>
<br>
/***** HCI ******/<br>
default object path:/org/bluez/Manager/hci (will use the default device in the kernel)<br>
object path: /org/bluez/Manager/hci0/hci<br>
object path: /org/bluez/Manager/hci1/hci<br>
interface: org.bluez.Manager.hci<br>
<br>
/***** SDP ******/<br>
default object path:/org/bluez/Manager/sdp<br>
object path: /org/bluez/Manager/hci0/sdp<br>
object path: /org/bluez/Manager/hci1/sdp<br>
interface: org.bluez.Manager.sdp<br>
<br>
/***** PAN ******/<br>
default object path:/org/bluez/Manager/pan<br>
object path: /org/bluez/Manager/hci0/pan<br>
object path: /org/bluez/Manager/hci1/pan<br>
interface: org.bluez.Manager.pan<br>
<br>
/***** RFCOMM ******/<br>
default object path:/org/bluez/Manager/rfcomm<br>
object path: /org/bluez/Manager/hci0/rfcomm<br>
object path: /org/bluez/Manager/hci1/rfcomm<br>
interface: org.bluez.Manager.rfcomm<br>
<br>
...<br>
(#1) Probably the display local devices should be moved to other path
due the permissions that I comment before. User&nbsp; applications
should be able list the local adapters to use in the pan, rfcomm, sdp
...<br>
<br>
<br>
For me, your suggestion or my last suggestion are fine, both can
address the permissions. You have the decision in your hands! :)<br>
<br>
<br>
Regards,<br>
Claudio<br><br><div><span class="gmail_quote">On 9/25/05, <b class="gmail_sendername">Marcel Holtmann</b> &lt;<a href="mailto:marcel@holtmann.org">marcel@holtmann.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Claudio,<br><br>&gt; Sorry, but the last patch(hcid_dbus_0007.patch) was not<br>&gt; based on the latest CVS version.<br><br>I realized that yesterday, but I am in Prague now for the UnPlugFest and<br>haven't had Internet access for two days. The patch looks good and I
<br>think we now have a nice and clean base to start with. However there are<br>some names I like to change. For example using org.bluez.Device for all<br>device specific configuration, like name changes. And org.bluez.Manager
<br>for Inquiry stuff etc. Do you think that makes sense?<br><br>Regards<br><br>Marcel<br><br><br><br><br>-------------------------------------------------------<br>SF.Net email is sponsored by:<br>Tame your development challenges with Apache's Geronimo App Server.
<br>Download it for free - -and be entered to win a 42&quot; plasma tv or your very<br>own Sony(tm)PSP.&nbsp;&nbsp;Click here to play: <a href="http://sourceforge.net/geronimo.php">http://sourceforge.net/geronimo.php</a><br>_______________________________________________
<br>Bluez-devel mailing list<br><a href="mailto:Bluez-devel@lists.sourceforge.net">Bluez-devel@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/bluez-devel">https://lists.sourceforge.net/lists/listinfo/bluez-devel
</a><br></blockquote></div><br>