espressif/esp-idf
1
0
Fork 1
mirror of https://github.com/espressif/esp-idf.git synced 2025-07-29 18:27:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

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

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

See merge request espressif/esp-idf!21265
This commit is contained in:
Jiang Jiang Jian
2022-11-30 15:59:06 +08:00
parent ee7953dc2a 6040bba236
commit 1d000363c6
2 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
components/wifi_provisioning/Kconfig
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.
@ -35,7 +34,6 @@ menu "Wi-Fi Provisioning Manager"
bool
prompt "Force Link Encryption during characteristic Read / Write"
depends on BT_NIMBLE_ENABLED
default y
help
Used to enforce link encryption when attempting to read / write characteristic

11
examples/provisioning/wifi_prov_mgr/README.md
View File

@ -261,6 +261,17 @@ Now erase NVS partition by running the following commands :
$IDF_PATH/components/esptool_py/esptool/esptool.py erase_region 0x9000 0x6000
```
### Bluetooth Pairing Request during provisioning
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 enable this functionality.
### Unsupported platform
If the platform requirement, for running `esp_prov` is not satisfied, then the script execution will fallback to console mode, in which case the full process (involving user inputs) will look like this :