Hi Partick and corentin, >This particular case is for Bluetooth input devices (keyboard, for example). >They need to be available and usable by the system before any particular user >is logged in. How to differentiate this from a non-shared device is up for >debate. BTW, as luiz's comments. "UserA requests to pair with DeviceR an authentication popup appears on UserA default screen (from DeviceL) and DeviceR allowing pairing UserB requests to pair with Device an authentication popup appears on UserB default screen (from DeviceL) and DeviceR allowing pairing UserA and UserB are paired with DeviceR'
This is currently impossible, if a second user attempts to pair it would invalid the first link key that is generated both locally and remotely, this could only work if each User has access to different local Adapter. My personal take is that Bluetooth settings should be restricted by a security policy, the application that pairs then has to set which users have access to that device which can be checked by e.g. dbus-daemon and it probably only make sense to restrict profiles that can access personal data, such as PBAP and MAP." Luiz suggest that Bluetooth settings should be restricted by a security policy. And any idea for how to differentiate this from a non-shared device? 1. send a request to Cynara with user id and application id params? And get the user related privileges? Or the other idea? Best Regards Zheng Wu -----Original Message----- From: Patrick Ohly [mailto:[email protected]] Sent: Tuesday, September 23, 2014 3:12 PM To: Zheng, Wu Cc: [email protected]; Le Foll, Dominique; [email protected] Subject: Re: [Dev] FW: Tizen 3 services: use case for multi user On Tue, 2014-09-23 at 06:41 +0000, Zheng, Wu wrote: > > Better: a device can be paired for one user and only used by that > > user; other devices get paired for use by all users (keyboards, for > > example). > I can understand a device can be paired for one user and only used by > that user; > > >other devices get paired for use by all users > UserA has paired with DeviceL and UserA can use the related service of > DeviceL. > If UserB want to use the related service of DeviceL, how can UserB do? > (UserA and UserB is in the same DeviceA). This particular case is for Bluetooth input devices (keyboard, for example). They need to be available and usable by the system before any particular user is logged in. How to differentiate this from a non-shared device is up for debate. -- 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
