[Dev] [NFC] OOB bluetooth pairing support is broken

VanCutsem, Geoffroy geoffroy.vancutsem at intel.com
Thu Oct 30 12:06:48 GMT 2014


Hi Corentin,

-----------------------------------------------
Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718.
Citibank, Brussels, account 570/1031255/09

From: Dev [mailto:dev-bounces at lists.tizen.org] On Behalf Of Corentin Lecouvey
Sent: Wednesday, October 29, 2014 2:46 PM
To: dev at lists.tizen.org
Subject: [Dev] [NFC] OOB bluetooth pairing support is broken

Hi all,

In order to move the bluetooth-frwk to NTB, I meet some problem with NFC.

Bluetooth contains OOB pairing mechanism which is based on NFC technology in order to pair close devices.
OOB feature is handled in bluetooth-frwk (client side) and it is supported by nfc-manager daemon (NFC server side).
[Geoffroy] Is this OOB feature something different than what I know as ‘NFC Bluetooth Handover’?

NFC manager uses bluetooth internal OOB API (not public C API).
Those internal bluetooth API have never been migrated to Bluez 5 and so can not work (https://bugs.tizen.org/jira/browse/TC-1971).
[Geoffroy] Shouldn’t the nfc-manager talk to neard which in terms communicate with BlueZ? I believe the latest neard version can handle both BlueZ 4 and 5.

NTB doesn't support OOB feature now. I made a Jira feature request here : https://bugs.tizen.org/jira/browse/TC-1970.

As it is just used on NFC server side and doesn't impact NFC Web device API, I would like to make OOB optionnal in nfc-manager-neard.

Does it make sense ?

Best regards,
Corentin

2014-10-29 11:16 GMT+01:00 Zheng, Wu <wu.zheng at intel.com<mailto:wu.zheng at intel.com>>:
Hi Corentin,

BTW, you can’t see any log of NTB on Tizen common. You need to setup dlog on basic Tizen common.

However, you can see the related log of NTB if you use Tizen IVI.

Best Regards
Zheng Wu

From: Corentin Lecouvey [mailto:corentin.lecouvey at open.eurogiciel.org<mailto:corentin.lecouvey at open.eurogiciel.org>]
Sent: Wednesday, October 29, 2014 6:01 PM
To: Zheng, Wu
Cc: Le Foll, Dominique; Xu, Martin; Jia, Pei P; dev at lists.tizen.org<mailto:dev at lists.tizen.org>
Subject: Re: Multi-user BT wiki

Hi Zheng Wu,


>1/ there is a problem with NFC stack.
Okay, maybe it need some modification to match bluetooth-frwk.

Yes, tizen-extensions-crosswalk requires the NFC stack in order to offer the Tizen NFC Web API.
If we move to NTB, NFC needs to be adapted to NTB.


>2/ NTB daemon should be fired by org.tizen.comms.service activation.
>Do you work on using a specific bluetooth user to manage tizen bluetooth stack ?
1. Yes. I can use "guest" user to run it well on tizen common and I didn't modify any configure.
2. To tizen common, Of course, The dbus configure file need to be modified to match the requirement of Tizen common.
 Not just for Common, for IVI as well...
OK. Let's use "guess" user for the moment to check multi-user implementation.


>3/ Bluez is blocked by RFkill.
Do tizen common use connman to enable/disable BT(including RFKILL)?
If so, I will modify the enable/disable BT.

Tizen Common will use NTB to enable/disable BT.
If some user wants to enable/disable BT over bluez, he will have to previously unblock bluetooth rfkill by himself.
NTB needs to include rfkill unblocking if needed.

Best regards,
Corentin




>I'm wondering how did you test it on Common. Can you let me know ?
Using "guest" user to run NTB daemon.
Using "Alice" user to run Bluez-capi-test
At the same time, Using "Bob" user to run Bluez-capi-test too.

Best Regards
Zheng Wu

-----Original Message-----
From: Corentin Lecouvey [mailto:corentin.lecouvey at open.eurogiciel.org<mailto:corentin.lecouvey at open.eurogiciel.org>]
Sent: Wednesday, October 29, 2014 12:34 AM
To: Zheng, Wu; Le Foll, Dominique; Xu, Martin; Jia, Pei P
Cc: dev at lists.tizen.org<mailto:dev at lists.tizen.org>
Subject: Re: Multi-user BT wiki

Hi Zheng Wu,

I wanted to check NTB on Tizen Common and I met several problems :

1/ there is a problem with NFC stack.
nfc-manager-neard component depends on libbluetooth-api.so which is an internal API inside bluetooth-frwk.
This package needs to be adapted to NTB in order to use core C API.

2/ NTB daemon should be fired by org.tizen.comms.service activation.
This service still depends on "app" user which is not in Common anymore.
NTB daemon can not be launched by dbus.
Do you work on using a specific bluetooth user to manage tizen bluetooth stack ?

3/ Bluez is blocked by RFkill.
NTB would have to handle this.
In Common bluetooth is power off after booting, I can not enable it unless I unblock bluetooth rfkill.

I'm wondering how did you test it on Common. Can you let me know ?

I will continue to review multi-user implementation.

Best regards,
Corentin



On 10/28/2014 02:50 AM, Zheng, Wu wrote:
> Hi all,
>
> NTB has implement the phase1 requirements of Multi-user BT.
>
> The following link is the related NTB wiki of Multi-user BT.
>
> https://wiki.tizen.org/wiki/NTB_Architecture#Multi-user_NTB
>
> Please check it. Thanks.
>
> Best Regards
> Zheng Wu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20141030/3edb278b/attachment-0001.html>


More information about the Dev mailing list