Luiz,
OK, that is a limitation that I forgot.
Fortunately as what we want to deliver is device isolation from various
users.
This will enforce that sharing devices between can only be done if the
pairing has been requested with the clear request to share in a similar
manner to what we are planing for network connection.
Corentin,
you will need to update the Wiki page to reflect that BT limitation.
- exclusive pairing request (default mode, available for any user)
Device can only be used by that user
- shared pairing (on request, restricted to Privilege users)
Device can be used by any user.
Shared pairing is not required in phase 1 if that can help
Dominig ar Foll
Senior Software Architect
Open Source Technology Centre
Intel SSG
Le 26/09/2014 10:28, Von Dentz, Luiz a écrit :
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
