mbed-os/features/FEATURE_BLE
Vincent Coubard 53ac45e03b
Bluetooth: Inform privacy risk of using signed writes.
The Cordio stack uses a single CSRK. It can be used by a
malicious device to track the Mbed OS application if signed
writes are used.

Signed-off-by: Vincent Coubard <vincent.coubard@arm.com>
2022-05-06 13:49:20 +01:00
..
ble Merge pull request #11204 from paul-szczepanek-arm/non-scan 2019-08-20 13:58:32 +02:00
source Added call to delete the security database object upon SM reset. This allows the file to be closed by the OS and flushed to disk. 2019-11-06 14:31:04 -05:00
targets Port Cordio LE Secure Connections check from PacketCraft 2020-04-22 10:58:27 +01:00
.gitignore Move ARMmbed/feature/FEATURE_BLE into mbedmicro/mbed. 2016-07-20 22:10:36 +01:00
.mbedignore BLE: Add unit test for the Generic GattClient. 2018-02-19 13:23:23 +00:00
CHANGELOG.md Move ARMmbed/feature/FEATURE_BLE into mbedmicro/mbed. 2016-07-20 22:10:36 +01:00
CONTRIBUTING.md Move ARMmbed/feature/FEATURE_BLE into mbedmicro/mbed. 2016-07-20 22:10:36 +01:00
DOXYGEN_FRONTPAGE_BLE.md Update doxygens to be in sync 2018-10-13 19:55:30 -05:00
LICENSE Move ARMmbed/feature/FEATURE_BLE into mbedmicro/mbed. 2016-07-20 22:10:36 +01:00
README.md Bluetooth: Inform privacy risk of using signed writes. 2022-05-06 13:49:20 +01:00
apache-2.0.txt Move ARMmbed/feature/FEATURE_BLE into mbedmicro/mbed. 2016-07-20 22:10:36 +01:00
ble.doxyfile Move ARMmbed/feature/FEATURE_BLE into mbedmicro/mbed. 2016-07-20 22:10:36 +01:00
mbed_lib.json UBLOX_EVK_ODIN_W2: Fix baremetal build and greentea tests 2019-11-22 10:55:39 +00:00

README.md

mbed Bluetooth Low Energy Stack

This is the Github repository for the BLE_API. Please see the Mbed OS Example BLE GitHub Repo for all code examples, and the Mbed OS BLE API page for all code documentation and general help.

Getting Started

Privacy notice

The Cordio Bluetooth stack only stores one single signing key. This key is then shared across all bonded devices. If a malicious device bonds with the Mbed OS application it then gains knowledge of the shared signing key of the Mbed OS device. The malicious device can then track the Mbed OS device whenever a signing write is issued from it.

To overcome this privacy issue do not issue signed writes from the Mbed OS device. A signed write occurs when the member function write of GattClient is called with its cmd argument set to GATT_OP_SIGNED_WRITE_CMD.

Instead of using signed writes, enable encryption on the connection. This is achieved by calling the function setLinkEncryption of the SecurityManager. Set the encryption to at least ENCRYPTED.