[Dev] Bluetooth multi-user feature
johan.hedberg at intel.com
Fri Sep 26 08:35:24 GMT 2014
This is not a software limitation. It's how all Bluetooth devices work
and how the Bluetooth specification is designed. There is no support for
multiple authentication keys pairs between two devices. Even if you'd
try to do tricks on our side you can't change the fact that re-pairing
with any device will have that device replace its old key with the new
one (from the new pairing).
On Fri, Sep 26, 2014, Dominig ar Foll (Intel OTC) wrote:
> 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 :
> >* 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
> ><corentin.lecouvey at open.eurogiciel.org> wrote:
> >>I've made a new bluetooth multi-user wiki page following a coherent
> >>integration process.
> >>That should be clearer.
> >>Best regards,
> >>Dev mailing list
> >>Dev at lists.tizen.org
> >Dev mailing list
> >Dev at lists.tizen.org
> Dev mailing list
> Dev at lists.tizen.org
More information about the Dev