Patrick: > > I've argued that it is the latter (see also > https://bugs.tizen.org/jira/browse/TC-1411) while the NTB developers claim > that the less secure access control in NTB is good enough for 3.0.
Please let me know Where you can find that "that NTB developers claim that the less secure access control in NTB is good enough for 3.0."??? Stop misleading people here, please!!!! Let me repeat the Multi-user status one more time, I do not want to repeat again. !!!! When we start to work on multi-user support, Dominique show us 4 phrase Multi-user support, after our evaluation, we found that we can only support phrase 1 just from NTB Base on the concept that Tizen applications must go through CAPI to get Bluetooth servicer. So after negotiate with Dominique, we will just implement phrase 1 before merge NTB into Tizen-3.0. After that we will work with BlueZ upstream to find the proper solution. I have answered your question many times. Tizen Bluetooth application can't have supper right to do everything directly to BlueZ or other system resource. It must go through CAPI to get system resource, and under some security control. That is what I understand of the _basic_ Tizen concept. That is what I learned during past years working on Tizen. If you think that is not right, please tell me what is the right concept? Thanks! _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
