On Tue, 2014-09-23 at 09:53 +0000, Zheng, Wu wrote: > >What prevents a rogue user process from ignoring NTB and using obexd and/or > >the system's Bluetooth support directly (i.e. replicate obexd inside the > >process > >itself)? > > It need to be analyzed cases by cases.
If you don't know, then check it first. If it turns out to be impossible, then it might not be worth implementing access control in NTB at all because it will have to be done again elsewhere (kernel?). Even if it turns out to be feasible, then it cannot be turned on without first ensuring that all uses of Bluetooth go through NTB. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
