Merge branch 'bugfix/disable_prov_encryption_v4.4' into 'release/v4.4'

Wifi Prov: Disabled the default support for BLE Encrpytion on characteristics read /write (v4.4)

See merge request espressif/esp-idf!21264
This commit is contained in:
Jiang Jiang Jian
2022-11-30 12:06:08 +08:00
2 changed files with 2 additions and 4 deletions

View File

@@ -19,7 +19,6 @@ menu "Wi-Fi Provisioning Manager"
bool
prompt "Enable BLE bonding"
depends on BT_ENABLED
default y
help
This option is applicable only when provisioning transport is BLE.
@@ -34,7 +33,6 @@ menu "Wi-Fi Provisioning Manager"
config WIFI_PROV_BLE_FORCE_ENCRYPTION
bool
prompt "Force Link Encryption during characteristic Read / Write"
default y
help
Used to enforce link encryption when attempting to read / write characteristic

View File

@@ -265,13 +265,13 @@ $IDF_PATH/components/esptool_py/esptool/esptool.py erase_region 0x9000 0x6000
### Bluetooth Pairing Request during provisioning
ESP-IDF now enforces link encryption requirement while performing GATT write on characteristics of provisioning service. This results in a pairing pop-up dialog, if link is not encrypted. This feature is enabled by default. In order to disable this feature and fallback to earlier behaviour of no pairing pop up during provisioning, please set CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION=n in the sdkconfig or unselect the configuration using "idf.py menuconfig" .
ESP-IDF now has functionality to enforce link encryption requirement while performing GATT write on characteristics of provisioning service. This will however result in a pairing pop-up dialog, if link is not encrypted. This feature is disabled by default. In order to enable this feature, please set `CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION=y` in the sdkconfig or select the configuration using "idf.py menuconfig" .
```
Component Config --> Wi-Fi Provisioning Manager --> Force Link Encryption during Characteristic Read/Write
```
Recompiling the application with above changes should suffice to disable this functionality.
Recompiling the application with above changes should suffice to enable this functionality.
### Unsupported platform