安全连接与BLE配对有什么参考资料吗？

你好阿古斯塔
你用哪种芯片？
当做
詹森



     以下为原文
  Hi Agusta
 
Which chip do you use?
 
Regards
Jenson

你好，我有CYW4338 BT芯片和STMF4 MCU。
一般做法是什么样的？加密数据本身，并写入特性时，只是'连接'（未配对）或配对与设备和发送未加密的数据（依靠BLE安全性）？
意志改变
SturyTyRealEngultIsMask= BtMySeCyn-无
到
SurvivyAdvaseIsMask= BtMySeCype加密
通过BLE控制器确保某种程度的加密？这与在BLL WiFi导入器中演示的安全密钥交换有什么不同。对此的一些澄清会很有帮助。



     以下为原文
  Hello, I have the CYW43438 bt chip and STMF4 mcu.
What is the general practice like? To encrypt data yourself and write to the characteristic when just 'connected' (not paired) OR pairing with the device and sending un-encrypted data (relying on BLE security) ?
Will changing

.security_requirement_mask = BTM_SEC_NONE

to

.security_requirement_mask = BTM_SEC_ENCRYPT

ensure some level of encryption by the ble controller? How is this different from secure passkey exchange demonstrated in ble wifi introducer for example. Some clarification on this would be really helpful.

使用蓝牙指定的默认加密程序将比试图从应用程序加密数据要好。
您可以使用WijdTBTyDeViSeCixBydand（）API请求对等设备配对和绑定。
LealSythIsRealEddieType面罩不用于LE，因此您可以省略它。



     以下为原文
  Using the default encryption procedure specified by Bluetooth would be better than trying to encrypt the data from application.
You could use the wiced_bt_dev_sec_bond() API to request the peer device for pairing and bonding.
 
The .security_requirement_mask is not used for LE, so you can omit it.

YSSU是否需要与WICDEXBTVDEVSET加密（）API一起使用WiDeTyBTyDeViSeCixBooDeNo.（）API（即，一旦配对完成，是否需要显式设置加密？在密钥交换/配对完成后，连接是否保证安全？我试图在BtMyPARIGIN完成的EVT事件中添加WICEDEXBTYDEVSETIOSCOMPATION（）函数，但我得到NOY资源错误8034。我不确定这是否需要，如果你能澄清的话，那就太好了。
此外，WICDEDH-BTYDEVGETGETBONDEDY DEVICESE（）API似乎不被支持，所以为了能够配对多个设备，我们需要存储对等设备的蓝牙地址和它在DCT中的相应密钥吗？结构WITDEXBTI DEVICES-LIKKYKESSHT存储与公共地址不匹配的静态LE地址，所以这些地址和它们的密钥需要存储在一些自定义结构中（这是可行的，但如果有更好的方法我想知道）。谢谢！



     以下为原文
  yssu Does the wiced_bt_dev_sec_bond() API need to be used in conjunction with the wiced_bt_dev_set_encryption() API, ie once pairing is complete do we need to set the encryption explicitly? Is the connection guaranteed to be secure after the keys are exchanged/pairing is complete? I tried to add wiced_bt_dev_set_encryption() function in the BTM_PAIRING_COMPLETE_EVT event but I get NO_RESOURCES error 8034. I am not sure if this is required, it'd be great if you could clarify.
Additionally, the wiced_bt_dev_get_bonded_devices() API doesnt seem to be supported, so in order to be able to pair multiple devices, do we need to store the bluetooth address of the peer device and it's corresponding keys in DCT? The struct wiced_bt_device_link_keys_t stores the static LE address which doesn't match with the public one, so do these addresses and their keys need to be stored in some custom struct (which is doable, but if there is a better way I'd like to know). Thanks!

-你不需要显式调用wiced_bt_dev_set_encryption()。wiced_bt_dev_sec_bond() API会照顾加密链接一旦设备配对。
-你需要存储节点设备键NVRAM btm_paired_device_link_keys_update_evt事件下。你可以使用wiced_hal_write_nvram() API将数据存储到NVRAM。
在wiced_bt_device_link_keys_t结构的公共地址和随机地址是。wiced_bt_device_link_keys_t - >；wiced_bt_device_address_t给出随机地址（如果同行使用）和wiced_bt_device_link_keys_t - >；wiced_bt_device_sec_keys_t具有对等设备ID地址。



     以下为原文
  - You don't have to explicitly call wiced_bt_dev_set_encryption(). wiced_bt_dev_sec_bond() API will take care of encrypting the link once the devices are paired.
 
- You need to store the peer device keys to NVRAM under the BTM_PAIRED_DEVICE_LINK_KEYS_UPDATE_EVT event. You can use the wiced_hal_write_nvram() API to store the data to NVRAM.
 
- In the wiced_bt_device_link_keys_t struct, both the public address and the random address are present. wiced_bt_device_link_keys_t->wiced_bt_device_address_t gives the random address (if used by the peer) and the wiced_bt_device_link_keys_t->wiced_bt_device_sec_keys_t has the ID address of the peer device.