I think you touched a topic that's problematic from a security point of view too.
Suppose the following: 1. Connect to a device that will use the iPhone as a peripheral to write to (ImmediateAlert service is a good example) 2. The device now can execute write requests on the iPhone and you will receive the corresponding CBPeripheralManager delegate calls 3. Disconnect from the device and start scanning for a different one
4. (THE ISSUE) The previous device is still able to write the phone and your app probably has no means to validate the calls as the sender info is not part of the write request data structure.
I may be missing something but this is in part a consequence of the removal of the centralDidConnect/Disconnect calls from the interface. This way the peripheral role has no info about the connected centrals. But also the fact that the write requests do not allow the identification of the sender central.
Thanks, Andras
hi,
can an ios app running in peripheral
role proactively terminate an active
connection??? i don't see any methods in CBPeripheralManager or CBCentral
that would support this....
thanks....
bob.
Bob Frankel, CTO
Emmoco, Inc |
Embedded Mobile Control
c: +1-805-680-0112
e: email@hidden
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|