Hi Patrick, 1. >Can you describe the entire design, not just what you are changing? I assume that you will have to add some kind of access control somewhere to restrict device access. The goal is to explain why these controls cannot be circumvented. At current NTB bt daemon use system dbus bus to implement NTB daemon method call.
However, if so, NTB daemon only run once. It means that NTB daemon only run on userA or userB.( system dbus will limit it) I will modify the interface method call of NTB daemon to session dbus. It means that NTB daemon only run on userA and userB. I don't modify any logic of NTB, just a little modification (modify system dbus interfaces to session dbus interfaces). Best Regards Zheng Wu -----Original Message----- From: Patrick Ohly [mailto:[email protected]] Sent: Tuesday, September 23, 2014 3:18 PM To: Zheng, Wu Cc: [email protected]; [email protected] Subject: Re: [Dev] FW: Tizen 3 services: use case for multi user On Tue, 2014-09-23 at 06:45 +0000, Zheng, Wu wrote: > Hi Patrick, > > >Please describe your design first before implementing it. Relevant are the > >process and user/kernel boundaries and how different components communicate > >with each other. > In fact, NTB use system dbus bus to implement bt agent, it only run on a user. > > I just modify system dbus bus to session dbus bus, so that NTB can run in > each normal user. No more. Can you describe the entire design, not just what you are changing? I assume that you will have to add some kind of access control somewhere to restrict device access. The goal is to explain why these controls cannot be circumvented. -- 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
