BLE Encrypted Connection

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
Thomas Donhauser
Offline
Last seen:4 months 2 weeks ago
加入:2019-10-20 10:45
BLE Encrypted Connection

Hello,

I have difficulties to determine if my peripheral BLE connection ist encrypted or not. In my device configuration this value

service_config.sec_level = GAP_SEC_LEVEL_1

is set. I'm using GAP_SEC_LEVEL_1 to ease the connection and pairing. This is done by the corresponding apps for iOS and Android. Also in the configuration

#define dg_configBLE_SECURE_CONNECTIONS (1)

is set. All I want to know is if the BLE-Communication is encrypted (LE Secure Connections) with my configuration or not.

PS.: I dicovered this in gap.h:

/// Unauthenticated pairing with encryption

GAP_SEC1_NOAUTH_PAIR_ENC,

Can you tell how to set this?

Thank you
Thomas

Device:
PM_Dialog
Offline
Last seen:6 hours 4 min ago
工作人员
加入:2018-02-08 11:03
Hi Thomas,

Hi Thomas,

Please take a look at the Bond Management Service (BMS) demo application which is provided within the SDK. This application code is located under SDK_10.0.8.105\projects\dk_apps\ble_profiles\bms path and it is using LE Secure Connections. If dg_configBLE_SECURE_CONNECTIONS macro is set to 1, LE Secure Connections feature is used during pairing if the peer supports the feature. Otherwise, LE Legacy Pairing is used.

Regarding the LE Secure Connections, please refer toUM-B-092: DA1469x Software Platform Reference Manualdocument and section 5.1.3.1. LE Secure

LE Secure Connections pairing is supported and enabled by default by the SDK using the API described in sections 5.1.3.2 LE Secure Connections pairing will be used if the connected peer supports the feature without the need for the application to specifically request it. If the combination of the devices’ capabilities result in a numeric comparison pairing algorithm (introduced and used for the LE Secure Connections pairing), the application will be notified of a numeric comparison request during pairing by the reception of a BLE_EVT_GAP_NUMERIC_REQUEST event and should respond using ble_gap_numeric_reply() function.

If the application needs to use only LE Legacy Pairing and disable LE Secure Connections support in the SDK, it should define dg_configBLE_SECURE_CONNECTIONS macro to 0 in the application config file.

Thanks, PM_Dialog

Thomas Donhauser
Offline
Last seen:4 months 2 weeks ago
加入:2019-10-20 10:45
Hello,

Hello,

Your answer does't help very much, because I'm using the da14683 and not the 1469x and the SDK I'm using therefor is SDK_1.0.14.1081.

The reason why I'm asking you is that I've read the docs forward and backward and I did't find out the answer. So sending me back to reading docs (the probably are not the right one) is not very much helpful.

So again: Does GAP_SEC_LEVEL_1 and #define dg_configBLE_SECURE_CONNECTIONS (1) provide encryption or not?

I wish you could answer my question in the way I've asked you.

regards,
Thomas

PM_Dialog
Offline
Last seen:6 hours 4 min ago
工作人员
加入:2018-02-08 11:03

Hi Thomas,

Sorry for the confusion. It’s my mistake regarding the product and the suggested document. Let me check again your initial question and I’ll get back to you shortly.

Thanks, PM_Dialog