On quinta-feira, 4 de agosto de 2016 22:48:49 PDT ??? wrote: > However there is no Public API related Android/Tizen platform. > the reason is that security issue and ble address is changing dynamic. > and the way you told is good suggestion. but since current ble address has > dynamic random address. it will be caused another issue.
Ah, I know what you're talking about. But isn't the address following a rule of formation? If not, how does peering work? There needs to be some form of credential that uniquely identifies a pairing. But that would mean it identifies the *pairing*. That information would be useless to a third device and should never be disclosed. Unless that third device establishes a new, direct pairing with the edge device, those two will never be able to connect and exchange information. So the RD case simply doesn't exist for BLE. Instead, BLE devices need to be "proxied", by a bridge or Resource Host. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
