Hi Luiz, You are right (Bluetooth pairing has been design it can only generate one link key for a given device).
To my understand, on Tizen system, the second user(such as userB) pairing is not real pairing, userB just want to share the privileges of the paired remote devices. Best Regards Zheng Wu -----Original Message----- From: Dev [mailto:[email protected]] On Behalf Of Von Dentz, Luiz Sent: Friday, September 26, 2014 4:28 PM To: Dominig ar Foll (Intel OTC) Cc: [email protected] Subject: Re: [Dev] Bluetooth multi-user feature Hi Dominig, Im pretty sure you got this wrong, this has nothing to do with BlueZ, it just the way Bluetooth pairing has been design it can only generate one link key for a given device, you can share that link key between but you cannot generate a new one because without invalidating the first one, this is how Bluetooth pairing works. On Fri, Sep 26, 2014 at 11:17 AM, Dominig ar Foll (Intel OTC) <[email protected]> wrote: > Luiz, > > you are stucked with what BlueZ can do. > If BlueZ does not want or cannot do what we need to enable Tizen user > private data protection , then it will have to be done somewhere else. > That is what there is a BT daemon in Tizen on top of BlueZ > > The good think with software is that nothing is impossible. It is just > a few extra line of code away. > > Dominig ar Foll > Senior Software Architect > Open Source Technology Centre > Intel SSG > > Le 26/09/2014 09:40, Von Dentz, Luiz a écrit : > >> Hi, >> >> * UserB can pair with deviceR only if userB uses his own credentials >> during pairing authentication with deviceR >> >> I guess I already mentioned this here, but I will keep repeating this >> is currently impossible, you cannot pair the same device with >> different users as Bluetooth has only one link key to authenticate >> and pairing again will erase the first link key. >> >> We do have a problem with certain profiles that can access private >> data, such as MAP and PBAP, this can either be blocked at D-Bus level >> or at the socket socket, the later is probably better but much more >> complicate since we need to have some sort of session API as was done >> for wifi but this has to be done directly in the kernel which Im not >> sure it would be worth it considering connman did that and nobody >> seems to use their session API. >> >> >> On Wed, Sep 24, 2014 at 6:48 PM, Corentin Lecouvey >> <[email protected]> wrote: >>> >>> Hi, >>> >>> I've made a new bluetooth multi-user wiki page following a coherent >>> integration process. >>> https://wiki.tizen.org/wiki/Multi-user_Bluetooth >>> >>> That should be clearer. >>> >>> Best regards, >>> Corentin >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> https://lists.tizen.org/listinfo/dev >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> https://lists.tizen.org/listinfo/dev > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
