ble_app_lecb L2CAP L2CAP app does not reject with Insuff. Auth. when necessary.

ID: LPCBARESDK-1057

Status: Fixed

First reported: 6.0.22.1401

Fixed in: 6.0.24.1464

Description

The ble_app_lecb application 6.0.22.1401\projects\target_apps\misc\ble_app_lecb demonstrates Bluetooth LE Credit-Based Flow Control for L2CAP Connection-Oriented Channels. For more details about connected oriented channel, refer to BLUETOOTH CORE SPECIFICATION Version 5.4 | Vol 3, Part A page 1164.

This application implements a dummy data exchange scenario between two peers in loopback mode. the user_app_lecb_connect_req_ind function check the security of the connection, This function replies always with success status, but if the security of the connection doesn’t match with the application security, this function should reply with rejection status.

void user_app_lecb_connect_req_ind(uint8_t conidx,
                                   struct gapc_lecb_connect_req_ind const *param, uint16_t *status)
{
    *status = L2C_CB_CON_SUCCESS;
}

Workaround

This is not considered as bug and doesn’t affect the SDK, the user should add his own rejection code to the application.