Securing access to s112 based device

RE: Securing access to s112 based device

yf13 — Tue, 28 Jan 2020 09:20:44 GMT

Thank you, I will spend more time with Glucose sample and BMS sample later.

RE: Securing access to s112 based device

Amanda Hsieh — Mon, 27 Jan 2020 14:49:08 GMT

Hi,

[quote user="yf13"]I tried the HRS example you mentioned but found that I can't run it directly on my nRF52DK, error logs are below:[/quote]

Sorry for that is a serialization example, you cannot run that standalone on 1 DK. You need 2 DK's, the other one need to run ble_connectivity, and you need to connect the boards as shown at this page... https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/nrf51_setups_serialization.html?cp=7_1_1_4

You could refer to <nRF5_SDK>\examples\ble_peripheral\ble_app_hrs\pca10040e\s112

The Bond Management Application is an example that demonstrates how to use the Bond Management Service. The example shows how to manage the storage of bond information and how to delete bonds after they have been established. For s112 project is under <nRF5_SDK_16.0.0>\examples\ble_peripheral\ble_app_bms\pca10040e\s112

[quote user="yf13"]Generally I am thinking to have my peripheral showing a random 4 digits passkey then ask the Android central app to enter it for bonding. [/quote]

You can take a look at the Glucose Application.

[quote user="yf13"]what are the proper params to achieve it with peer_manager? [/quote]

It looks correct. Please also see Peer Manager - Usage and the Glucose Application.

[quote user="yf13"]how many central peers can we have for a nRF peripheral? [/quote]

It's typically 4 different centrals. Please see this post.

-Amanda H.

RE: Securing access to s112 based device

yf13 — Sat, 25 Jan 2020 03:29:40 GMT

Thank you Amanda!

I tried the HRS example you mentioned but found that I can't run it directly on my nRF52DK, error logs are below:

<info> app_timer: RTC: initialized.
<warning> sphy_hci: Timeout, no ACK. Dropping.
<error> nrf_sdh_ble: sd_ble_cfg_set() returned NRF_ERROR_INTERNAL when attempting to set BLE_CONN_CFG_GAP.
<error> app: ERROR 17 [NRF_ERROR_BUSY] at /opt/nRF/components/serialization/application/transport/ser_sd_transport.c:304
PC at: 0x000158C7
<error> app: End of error report

Maybe I can't use that ser_s112_hci example directly on my nRF52DK board --- the name "ser_s112_hci" implies some special hardware configuration to me...

From the SDKv16 examples folder, I also noticed there is a "ble_app_bms" example, it seems like a BLE service based on the "peer manager" component? I made it to run on pca10040. after setting the USE_AUTHORIZATION_CODE to 0, I seemed can bond to it from the "nRF Connect" Android app.

<info> app_timer: RTC: initialized.
<info> app: Bond Management example started with 1 peers
<info> app: Fast adverstising.
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> app: Connected
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Encryption
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> app: Fast adverstising.
<info> app: Disconnected
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> app: Connected
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Encryption
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> app: Fast adverstising.
<info> app: Disconnected
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> app: Connected
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Encryption
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update, no change
<info> ble_bms: Control point write: Success
<info> app: Client requested that bond to current device deleted
<info> app: Fast adverstising.
<info> app: Disconnected
<error> peer_manager_handler: Peer deleted successfully: peer_id: 0
<info> app: Connected
<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102
<info> peer_manager_handler: Connection secured: role: Peripheral, conn_handle: 0, procedure: Bonding
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Bonding data, action: Update
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Peer rank, action: Update
<info> peer_manager_handler: Peer data updated in flash: peer_id: 0, data_id: Central address resolution, action: Update
<info> app: Fast adverstising.
<info> app: Disconnected

Currently I don't fully understand the BMS service yet, but I guess it allows us to delete an Android central from a peripheral so that the peripheral can bond with other Android central later. This is useful especially when the peripheral has no input buttons.

Generally I am thinking to have my peripheral showing a random 4 digits passkey then ask the Android central app to enter it for bonding. what are the proper params to achieve it with peer_manager?

sec_param.bond           = 1;
sec_param.mitm           = 1;
sec_param.lesc           = 1;
sec_param.keypress       = 0;
sec_param.io_caps        = BLE_GAP_IO_CAPS_DISPLAY_ONLY;
sec_param.oob            = 0;

Yet another question is how many central peers can we have for a nRF peripheral?

RE: Securing access to s112 based device

Amanda Hsieh — Fri, 24 Jan 2020 11:59:21 GMT

Hi,

I would suggest you take a look at nRF5 SDK v16.0.0: Peer Manager and start from Heart Rate Application.

HRS s112 example is under nRF5_SDK_16.0.0\examples\ble_peripheral\ble_app_hrs\pca10040\ser_s112_hci

-Amanda H.