Hello @Olivier L
I have tried implementing the OOB from the firmware you had provided, and from the little nuggets of information that I got from the site's discussion, I haven't been able to trigger OOB Byte in the firmware version binary 1.13.0. I am using an android Android app and device is STM32Wb series microcontroller. Irrespective of permutations and combinations that I have tried, connection always falls back to numeric pairing.. :(
My Goal is to have Preset OOB Key on Device(STM32WB) and Phone(currently android) to establish a secure connection.
- Added event mask to generate 256bit key after "aci_gap_set_authentication_requirement"
uint8_t ALL_EVENTS[8]={0x9F,0x01,0x00,0x00,0x00,0x00,0x00,0x00};
hci_le_set_event_mask(ALL_EVENTS);
int status = hci_le_read_local_p256_public_key();
APP_DBG_MSG("\r\n\r EVENT MASK To Generate a LOCAL 256 Key %d \n",status );
Added "HCI_LE_READ_LOCAL_P256_PUBLIC_KEY_COMPLETE_SUBEVT_CODE" event in
switch (meta_evt->subevent)
{
.// few more cases not shown for clarity
case HCI_LE_READ_LOCAL_P256_PUBLIC_KEY_COMPLETE_SUBEVT_CODE:
{
APP_DBG_MSG("\n\r OOB Key Gen Event!");
runOOB();
}
}
static void runOOB(void)
{
uint8_t at = 0x00;
uint8_t add[6] = {0x00,0x00,0x00,0x00,0x00,0x00};
uint8_t len = 0x10;
uint8_t random[16] = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0};
uint8_t confirm[16] = {0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0};
int status = aci_gap_set_oob_data(0x00,0x00,0x00, 0, 0, 0);
APP_DBG_MSG("\n\r OOB INITIALIZATION STATUS : %d", status);
int statusRand = aci_gap_get_oob_data(0x01, &at,add,&len, random);
int statusConfirm = aci_gap_get_oob_data(0x02, &at,add,&len, confirm);
APP_DBG_MSG("\n\r OOB Key - Random Data: [");
for(int i =0; i <16; i++)
APP_DBG_MSG("%02X:", random[i]);
APP_DBG_MSG("]");
APP_DBG_MSG("] \n\r OOB Key Hash : ");
for(int i =0; i <16; i++)
APP_DBG_MSG("%02X:", confirm[i]);
}
Lastly, I was wondering if you can advise on, if there is a way to hardcode the keys on the device and bypass the pairing completely, without bonding...? in our use case, secure connection takes 2000-2700 ms, which is very bad user experience.
