ソースを参照

qcacmn: Don't add pmkid count field in initial association

In the initial connection association request, since the STA
doesn't have pmkid, it sends the 2 byte pmkid field as 0.
But some APs dont allow pmkid count field to be 0 during
association and pmkid field having some value in EAPOL
handshake and triggers disconnection with reason code 17(
Information element in 4-way handshake different from Assoc
request). With crypto component disabled, the legacy
rsn ie construction doesn't add the 2 bytes with 0 value for
non-PMF connections.

So don't add pmkid count with 0 value in initial association
request for non-PMF connections.

Change-Id: I90441167ee480bf5d08e73e43d3ee9371bd16b0a
CRs-Fixed: 2783639
Pragaspathi Thilagaraj 4 年 前
コミット
79da1010f3
1 ファイル変更0 行追加2 行削除
  1. 0 2
      umac/cmn_services/crypto/src/wlan_crypto_global_api.c

+ 0 - 2
umac/cmn_services/crypto/src/wlan_crypto_global_api.c

@@ -3029,8 +3029,6 @@ add_rsn_caps:
 			WLAN_CRYPTO_ADDSHORT(frm, 1);
 			qdf_mem_copy(frm, pmksa->pmkid, PMKID_LEN);
 			frm += PMKID_LEN;
-		} else {
-			WLAN_CRYPTO_ADDSHORT(frm, 0);
 		}
 	}