Hi Corentin, >Is there a reason to run it as app user ? >It should be run on root mode.
Obex related features are necessary on app mode. Therefore, Our Bluetooht-Frwk need to run on app mode. Or Our Bluetooht-Frwk will miss the obex related features. The current design is that Bluetooht-Frwk run on app mode. Best regards Zheng Wu -----Original Message----- From: Corentin Lecouvey [mailto:[email protected]] Sent: Tuesday, September 2, 2014 4:52 PM To: Zheng, Wu Subject: Re: FW: Bluetooth TCT testing - socket Hi Zheng Wu, Please find my reply below. But Ideally app user doesn't exist in a multiuser environment because there should not contain pre-existing user. Btw, I think we should share this kind of discussion in dev list or Jira. Best regards, Corentin On 09/02/2014 10:32 AM, Zheng, Wu wrote: > Hi corentin, > > 1. For syspopup, I understand that it is your priority task. > You need to finish it. > > 2. For multiuser compliancy, in fact, I have some questions. > > Our Bluetooht-Frwk run on app mode, not root mode. Is there a reason to run it as app user ? It should be run on root mode. > > Can Security interfaces work on app mode? Security will be integrated according to user not just app. But the security will come later... > > Is it possible that add multiuser compliancy functions to Bluetooht-Frwk on > app mode? No it is not. app user should not be used anymore. We will introduced a multiuser policy in a central daemon (in bluetooth-service ?) that will verify who makes the request to BlueZ and forward it if necessary. > > I am not sure. > > What do you think? > > Best Regards > Zheng Wu > > -----Original Message----- > From: Corentin Lecouvey [mailto:[email protected]] > Sent: Tuesday, September 2, 2014 3:52 PM > To: Zheng, Wu > Subject: Re: FW: Bluetooth TCT testing - socket > > Hi Zheng Wu, > > Actually TCT bluetooth tests are no more my priority. > I will send t-e-c fixes to crosswalk github. > > My priority is NTB integration into Tizen:Common. > To achieve that, notifications-service adaptation and multiuser compliancy > have to be integrated. > If you have any ideas and/or comments about that, feel free to complete Jira > bugs. > > After finding a a way to detect agent correctly, I will propose a patch in > gerrit. > I understand now how it works with syspopup and I need to find a way to do > the same thing with notifications-service. > > Best regards, > Corentin > > > > On 09/02/2014 05:41 AM, Zheng, Wu wrote: >> Hi Corentin, >> >> How about TCT Bluetooth Test cases? >> >> Best Regards >> Zheng Wu >> >> -----Original Message----- >> From: Corentin Lecouvey >> [mailto:[email protected]] >> Sent: Saturday, August 30, 2014 1:16 AM >> To: Zheng, Wu >> Subject: Re: FW: Bluetooth TCT testing - socket >> >> Hi Zheng Wu, >> >> Thanks that solves my problem. >> >> I've made few socket fixes in my sandbox. >> I was able to send messages by socket and read them using >> tizen-extensions-crosswalk-examples. >> >> Best regards, >> Corentin >> >> >> On 08/29/2014 05:40 AM, Zheng, Wu wrote: >>> Hi corentin, >>> >>> Sorry, please use the devel branch of Bluez on >>> tizen.org.(platform/upstream/bluez) >>> >>> Best Regards >>> Zheng Wu >>> >>>> -----Original Message----- >>>> From: Zheng, Wu >>>> Sent: Friday, August 29, 2014 10:08 AM >>>> To: 'Corentin Lecouvey' >>>> Subject: RE: Bluetooth TCT testing - socket >>>> >>>> Hi Corentin, >>>> >>>> We have some patches to modify the Bluez to match Bluetooth-frwk socket. >>>> >>>> Please download and use the latest version of Bluez on >>>> Tizen.org.(platform/upstream/bluez) >>>> >>>> Best regards >>>> Zheng Wu >>>> >>>> -----Original Message----- >>>> From: Corentin Lecouvey >>>> [mailto:[email protected]] >>>> Sent: Thursday, August 28, 2014 9:52 PM >>>> To: Zheng, Wu >>>> Subject: Re: Bluetooth TCT testing - socket >>>> >>>> Hi Zheng Wu, >>>> >>>> I have some difficulties to establish a connection on a remote >>>> device using bluez-capi-test. >>>> >>>> Please find attached to this email many log files about what I did . >>>> This time, the bluetoothd running on server side told me that at >>>> socket connection attempt. >>>> Aug 28 06:34:16 common_box bluetoothd[250]: GAP and GATT are >>>> mandatory Aug 28 06:34:16 common_box bluetoothd[250]: >>>> gap-gatt-profile profile probe failed for 20:16:D8:D7:28:F4 Aug 28 >>>> 06:34:40 common_box bluetoothd[250]: spp rejected >>>> 20:16:D8:D7:28:F4: Type of message, `(os)', does not match expected >>>> type `(osh)' >>>> >>>> Could you please let me know if the bluez-capi-test commands >>>> sequences (on client and server sides) are right ? >>>> >>>>> Pay attention to "no any prompt" when connection. >>>>> Therefore, you need to enter a "Y"/"y" in Bluez-capi-test after >>>>> printing >>>> any connection. >>>> >>>> It is maybe my problem... >>>> >>>> >>>> Thanks in advance, >>>> Corentin >>>> >>>> >>>> On 08/28/2014 12:17 PM, Zheng, Wu wrote: >>>>> Hi corentin, >>>>> >>>>>> Aug 28 02:57:23 common_box bluetoothd[240]: Authentication >>>> attempt >>>>>> without agent Aug 28 02:57:23 common_box bluetoothd[240]: spp >>>>>> rejected >>>>>> 20:16:D8:D7:28:F4: org.bluez.Error.Rejected >>>>> Please use bluez-capi-test to register a agent. >>>>> >>>>> Bluez-capi-test: >>>>>> init_bluez >>>>>> enable >>>>>> register-agent >>>>> Pay attention to "no any prompt" when connection. >>>>> >>>>> Therefore, you need to enter a "Y"/"y" in Bluez-capi-test after >>>>> printing >>>> any connection. >>>>> Good luck. >>>>> >>>>> Best Regards >>>>> Zheng Wu >>>>> >>>>> -----Original Message----- >>>>> From: Corentin Lecouvey >>>> [mailto:[email protected]] >>>>> Sent: Thursday, August 28, 2014 6:11 PM >>>>> To: Zheng, Wu >>>>> Subject: Re: Bluetooth TCT testing - socket >>>>> >>>>> Hi Zheng Wu, >>>>> >>>>> Thanks for the tip ! >>>>> >>>>> The next step is an agent error !!! >>>>> Aug 28 02:57:23 common_box bluetoothd[240]: Authentication attempt >>>>> without agent Aug 28 02:57:23 common_box bluetoothd[240]: spp >>>> rejected >>>>> 20:16:D8:D7:28:F4: org.bluez.Error.Rejected >>>>> >>>>> Corentin >>>>> >>>>> On 08/28/2014 04:08 AM, Zheng, Wu wrote: >>>>>> Hi Corentin, >>>>>> >>>>>> The CHAT_SERVICE_UUID is not right in the bluetooth_common.js. >>>>>> >>>>>> The uuid doesn't provide PSM and channel for connection. >>>>>> >>>>>> Therefore we use "00001101-0000-1000-8000-00805f9b34fb" to test. >>>>>> >>>>>> Please modify CHAT_SERVICE_UUID to >>>> "00001101-0000-1000-8000-00805f9b34fb" >>>>>> Best Regards >>>>>> Zheng Wu >>>>>> >>>>>> -----Original Message----- >>>>>> From: Corentin Lecouvey >>>>>> [mailto:[email protected]] >>>>>> Sent: Thursday, August 28, 2014 12:08 AM >>>>>> To: Zheng, Wu >>>>>> Subject: Bluetooth TCT testing - socket >>>>>> >>>>>> Hi Zheng Wu, >>>>>> >>>>>> I updated my sandbox with 2 fixes. It is a start point to make >>>>>> work socket >>>> connections... >>>>>> When calling bt_socket_connect_rfcomm(), BlueZ tells me : >>>>>> bluetoothd[244]: Failed to find L2CAP PSM or RFCOMM >>>>>> channel >>>> for >>>>>> spp >>>>>> >>>>>> Let's continue tomorrow... >>>>>> Best regards, >>>>>> Corentin >>>>>> >>>>>> _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
