esp_wifi: Always connect Station in PMF mode if possible

While using esp_wifi_set_config, flag pmf_capable defaults to 0.
Users may not bother to enable it, which prevents connection to a
WPA3 AP. Or the AP may reset into WPA3 mode failing the re-connection.
To ensure better security, deprecate the pmf_capable flag and set it to
true internally.
Additionally add API esp_wifi_disable_pmf_config to disable PMF for
debug purposes or to avoid PMF issues on AP side.

components/esp_wifi/include/esp_wifi.h

@@ -1113,6 +1113,19 @@ esp_err_t esp_wifi_get_inactive_time(wifi_interface_t ifx, uint16_t *sec);
   */
 esp_err_t esp_wifi_statis_dump(uint32_t modules);
 
+/**
+  * @brief      Disable PMF configuration for specified interface
+  *
+  * @attention  This API should be called after esp_wifi_set_config() and before esp_wifi_start().
+  *
+  * @param      ifx  Interface to be configured.
+  *
+  * @return
+  *    - ESP_OK: succeed
+  *    - others: failed
+  */
+esp_err_t esp_wifi_disable_pmf_config(wifi_interface_t ifx);
+
 #ifdef __cplusplus
 }
 #endif

components/esp_wifi/include/esp_wifi_types.h

@@ -207,7 +207,7 @@ typedef enum {
 
 /** Configuration structure for Protected Management Frame */
 typedef struct {
-    bool capable;            /**< Advertizes support for Protected Management Frame. Device will prefer to connect in PMF mode if other device also advertizes PMF capability. */
+    bool capable;            /**< Deprecated variable. Device will always connect in PMF mode if other device also advertizes PMF capability. */
     bool required;           /**< Advertizes that Protected Management Frame is required. Device will not associate to non-PMF capable devices. */
 } wifi_pmf_config_t;
 

components/esp_wifi/lib

@@ -1 +1 @@
-Subproject commit 26f513178728f89ac8a48c71ec390ac776640a7f
+Subproject commit 582a616c629f26d6c034edbaba24abee44295fac

docs/en/api-guides/wifi.rst

@@ -1416,13 +1416,34 @@ An attacker can use eavesdropping and packet injection to send spoofed (de)authe
 
 PMF provides protection against these attacks by encrypting unicast management frames and providing integrity checks for broadcast management frames. These include deauthentication, disassociation and robust management frames. It also provides Secure Association (SA) teardown mechanism to prevent spoofed association/authentication frames from disconnecting already connected clients.
 
-ESP32 supports the following three modes of operation with respect to PMF.
+There are 3 types of PMF configuration modes on both Station and AP side -
+ - PMF Optional
+ - PMF Required
+ - PMF Disabled
 
- - PMF not supported: In this mode, ESP32 indicates to AP that it is not capable of supporting management protection during association. In effect, security in this mode will be equivalent to that in traditional mode.
- - PMF capable, but not required: In this mode, ESP32 indicates to AP that it is capable of supporting PMF. The management protection will be used if AP mandates PMF or is at least capable of supporting PMF.
- - PMF capable and required: In this mode, ESP32 will only connect to AP, if AP supports PMF. If not, ESP32 will refuse to connect to the AP.
+Depending on the PMF configuration on Station and AP side, the resulting connection will behave differently. Below table summarises all possible outcomes.
 
-:cpp:func:`esp_wifi_set_config` can be used to configure PMF mode by setting appropriate flags in `pmf_cfg` parameter. Currently, PMF is supported only in Station mode.
++--------------+------------------------+---------------------------+
+| STA Setting  | AP Setting             |  Outcome                  |
++==============+========================+===========================+
+| PMF Optional |  PMF Optional/Required | Mgmt Frames Protected     |
++--------------+------------------------+---------------------------+
+| PMF Optional |  PMF Disabled          | Mgmt Frames Not Protected |
++--------------+------------------------+---------------------------+
+| PMF Required |  PMF Optional/Required | Mgmt Frames Protected     |
++--------------+------------------------+---------------------------+
+| PMF Required |  PMF Disabled          | STA refuses Connection    |
++--------------+------------------------+---------------------------+
+| PMF Disabled |  PMF Optional/Disabled | Mgmt Frames Not Protected |
++--------------+------------------------+---------------------------+
+| PMF Disabled |  PMF Required          | AP refuses Connection     |
++--------------+------------------------+---------------------------+
+
+{IDF_TARGET_NAME} supports PMF only in Station mode. Station defaults to PMF Optional mode and disabling PMF is not possible. For even higher security, PMF Required mode can be enabled by setting the ``required`` flag in `pmf_cfg` while using the :cpp:func:`esp_wifi_set_config` API. This will result in Station only connecting to a PMF enabled AP and rejecting all other AP's.
+
+.. attention::
+
+    ``capable`` flag in `pmf_cfg` is deprecated and set to true internally. This is to take the additional security benefit of PMF whenever possible.
 
 
 WPA3-Personal

examples/wifi/getting_started/station/main/station_example_main.c

@@ -86,11 +86,6 @@ void wifi_init_sta(void)
              * However these modes are deprecated and not advisable to be used. Incase your Access point
              * doesn't support WPA2, these mode can be enabled by commenting below line */
 	     .threshold.authmode = WIFI_AUTH_WPA2_PSK,
-
-            .pmf_cfg = {
-                .capable = true,
-                .required = false
-            },
         },
     };
     ESP_ERROR_CHECK(esp_wifi_set_mode(WIFI_MODE_STA) );

examples/wifi/iperf/main/cmd_wifi.c

@@ -136,7 +136,6 @@ static bool wifi_cmd_sta_join(const char* ssid, const char* pass)
     int bits = xEventGroupWaitBits(wifi_event_group, CONNECTED_BIT, 0, 1, 0);
 
     wifi_config_t wifi_config = { 0 };
-    wifi_config.sta.pmf_cfg.capable = true;
 
     strlcpy((char*) wifi_config.sta.ssid, ssid, sizeof(wifi_config.sta.ssid));
     if (pass) {