RE: Security as Central a

Edvin — Fri, 09 Aug 2019 09:19:47 GMT

Hello,

If you look at the on_ble_evt() function in main.c, it calls pm_handler_secure_on_connection(p_ble_evt); before the switch(p_ble_evt->header.evt_id).

If you look in the case BLE_GAP_EVT_CONNECTED inside the pm_handler_on_secure_connection() function you see that it will secure the connection using conn_secure();

You can try to do this only if it is a peripheral or a central connection. If you are connecting to a phone, and you don't want to encrypt this connection, I assume that the phone acts as a central, and the nRF as a peripheral in this connection.

The BLE_GAP_EVT_CONNECTED has a variable called role, which you can see in ble_gap.h on line 1016.

Try to add a check to see if the nRF is a peripheral or a central in this connection, and only secure the connection if you are a central in your on_ble_evt() in main.c:

static void on_ble_evt(uint16_t conn_handle, ble_evt_t const * p_ble_evt)
{
    char        passkey[BLE_GAP_PASSKEY_LEN + 1];
    uint16_t    role = ble_conn_state_role(conn_handle);

    if (p_ble_evt->evt.gap_evt.params.connected.role == BLE_GAP_ROLE_CENTRAL)
    {
        pm_handler_secure_on_connection(p_ble_evt);
    }

    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
            m_connected_peers[conn_handle].is_connected = true;
            m_connected_peers[conn_handle].address = p_ble_evt->evt.gap_evt.params.connected.peer_addr;
            multi_qwr_conn_handle_assign(conn_handle);
            break;
        case ...

Best regards,

Edvin