CC2564: CC256X bluetopia LE OOB

Isn’t that recommendation a non secure connection legacy just work pairing only? I mean it doesn’t follow the spec flow and only bypass the pin number (which I guess should be set as display and keyboard capable device to make this work.

I was looking for something more inline with the spec that exchange the oob data (hash and randomizer) and cteate a secure connection. Maybe I don’t understand something but the bluetooth spec  seem to give some clear HCI steps on this. My question is the bluetopia and gap layer: can they be used to perform the specs flow and simplify this flow? if so, how and where the oob data enter into play with those? or do I need to use the HCI Api only to perform the oob pairing from the host?

Hi, thanks for the info. I was under the impression the SCGenerateOOBLocalParams was only for the LE Legacy Secure Simple Pairing (4.0/4.1) and the doc seem to be into this way too.

http://processors.wiki.ti.com/index.php/CC256x_TI_Bluetooth_Stack_CSCPDemo_App#SCGenerateOOBLocalParams

I'm still not sure what is required to be exchanged for an OOB LE Secure Connection (full 4.2, not a Just Work nor a legacy pairing). I'm a bit at lost with all the connections type but I would like a secure authenticated/encrypted connection (require as little as possible exchange between devices and use the most of the oob link prior to start connecting the device).

I will go and try a normal secure connection with whitelist of oob address received only. I guess giving both IO capbability OOB will request me something special at some point where I will have to figure out what is required to be exchange between device into OOB link and will be filled into some events (both side I think).

Maybe I'm missing a main concept here,

Thanks for the help

Hi again, I'm still struggling with a few concept of OOB, this follow my last finding, now that I known I only have Bluetooth 4.0 (Bluetopia 4.0.2.2) with my radio and stack I wonder if the Le Legacy - Secure Simple Pairing is possible? I can generate and exchange the OOB  using:

GAP_Query_Local_Out_Of_Band_Data(GAP_Out_Of_Band_Data_t*)

which give me the hash and the rand. I already pass this data over my OOB link along with the public address. Each device then white list each other and the peripheral start advertise to the white list address and the central start scanning with white filter enabled.

Device connect. I should now give my IO capability (No IO on both device in my case) and set the OOB flag. After this, according to those link:

https://blog.bluetooth.com/bluetooth-pairing-part-5-legacy-pairing-out-of-band

https://community.nxp.com/thread/332191

I should receive and confirm with OOB data with the C1() and S1 function. But the second link seem to indicate this was introduced into 4.1 specs and I can't find them into Bluetopia 4.0.2.2. Is Le Legacy - Secure Pairing OOB with hash/rand possible with this stack or I'm chasing a ghost again?

With this stack is possible or built-in?

If this is not implemented/possible, I probably will make a pin key exchange on OOB (4-6 number?) and use IO capability on the master for keyboard/display and display on peripheral device and simulate user action to authenticate? That would be an ugly hack but could work I think (if the pin number can be enforced on the peripheral and is not generated by the stack at the display time).

Thanks for your help, it's appreciated

Jerome

To add some information which might help or clarify:
I just checked the 4.0 specs and I want to achieve the security mode 1 level 3, I guess this should be possible with OOB.
When I have to fill the

GAP_LE_Authentication_Response_Information_t
{
  ...
  {
    GAP_LE_OOB_Data_t Out_Of_Band_Data
    {
       Encryption_Key_t OOB_Key
    }
    ...
  } Authentication_Data
}

this is only a single key Encryption_Key_t, which is the result of c1() function call (if I'm not mistaken from the oob hash and rand). Is the C1 function implemented into the stack or should I create it?