Hi,
In a phone call Dominig recently added that a weaker requirement might
also be acceptable: instead of requiring that two different users can
pair with the same remote device and use it alternating and/or
concurrently, allow a device to be paired with exactly one user and
prevent access to it by any other user.
Yes, that is a first acceptable phase indeed.
I remind that the main goal is to NOT share user credentials and
connections with a remote device.
In short terms, this solution respects our main requirements and so is
sufficient to integrate NTB into tizen.
Btw let me re-write a multi-pairing use case I wrote at the very bottom
of my previous mail...
That reply to
And I think the reason why we want to support multi-paring is just to
protect the
personal date for PBAP, MAP and so on, which is our second request.
However, PBAP, MAP, FTP, OPP are all based on OBexd, and run at
normal user
privilege not root, and each has it's own default home directory
bound with the
user to share the data through Bluetooth.
So that means for above profiles, the multi-user are supported natively.
We just did not try and verify the scenario before, but I think it
will not big issue
here, we will have a try on it.
BlueZ 5 persistently pairs remote devices, which brings up a use case
for multi-pairing :
UserA is paired and connected to deviceR. When userA is disconnected
from deviceR, userA stays paired.
In such case, a new user (userB) logins to the system and he is
automaticaly paired to deviceR without any authentication.
As userB is already paired with the remote deviceR, he can just connect
to PBAP service from deviceR to retrieve the phonebook for example.
Best regards,
Corentin
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
