Access without giving a passkey

RE: Access without giving a passkey

Sietse — Thu, 15 Sep 2022 14:01:21 GMT

Hello, it is working now!

I, ad hoc, patched ble_nus_init() to use SEC_JUST_WORKS, with is enough for me.

In the BLE_GAP_EVT_AUTH_STATUS case I did

             if (p_ble_evt->evt.gap_evt.params.auth_status.auth_status == 0x89) {
               err_code = sd_ble_gap_disconnect(p_ble_evt->evt.gattc_evt.conn_handle,
                                                BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
               APP_ERROR_CHECK(err_code);
             }

Thanks for the help, Sietse

RE: Access without giving a passkey

Hung Bui — Thu, 15 Sep 2022 11:29:08 GMT

Hi Sietse,

We would need to look at how you configure your characteristic and service read/write access.

Note that by default BLE doesn't have any mechanism to terminate a connection if the link is not bonded/encrypted. It's up to the application to decide if it needs to terminate the connection due to lack of encryption/security level.

However, in your service/characteristic you can configure the level of encryption needed to access the characteristic/service. You can find that in the configuration of read_access and write_access in ble_nus_init() function.
By default they are SEC_OPEN, but you can change to SEC_JUST_WORKS or SEC_MITM etc to limit the access if the link is not bonded. Please refer to the gls example.

In addition to that, if you want to terminate the connection if the link is not encrypted you can implement in your application code to check if the BLE_GAP_EVT_AUTH_STATUS doesn't return BLE_GAP_SEC_STATUS_SUCCESS and you can terminate the connection using sd_ble_gap_disconnect().

RE: Access without giving a passkey

Sietse — Wed, 14 Sep 2022 12:02:59 GMT

devzone.nordicsemi.com/.../807051.main.c