aboutsummaryrefslogtreecommitdiffstats
path: root/toolchain/kernel-headers
diff options
context:
space:
mode:
authorLeon M. Busch-George <leon@georgemail.eu>2022-11-23 17:40:08 +0100
committerChristian Marangi <ansuelsmth@gmail.com>2023-02-19 19:43:57 +0100
commitae751535de0cb46978bfcbacab882dd1082e59e3 (patch)
treec3e725ba6019f92c6288e71db9ffddf736a8681e /toolchain/kernel-headers
parent3c10c42ddd4741615b896e1d429ac7d6e91a980f (diff)
downloadupstream-ae751535de0cb46978bfcbacab882dd1082e59e3.tar.gz
upstream-ae751535de0cb46978bfcbacab882dd1082e59e3.tar.bz2
upstream-ae751535de0cb46978bfcbacab882dd1082e59e3.zip
hostapd: always use sae_password for mesh/SAE auth
This patch fixes a corner case when using passwords that are exactly 64 characters in length with mesh mode or passwords longer than 63 characters with SAE because 'psk' is used instead of 'sae_password'. SAE is obligatory for 802.11s (mesh point). The 'psk' option for hostapd is suited for WPA2 and enforces length restrictions on passwords. Values of 64 characters are treated as PMKs. With SAE, PMKs are always generated during the handshake and there are no length restrictions. The 'sae_password' option is more suited for SAE and should be used instead. Before this patch, the 'sae_password' option is only used with mesh mode passwords that are not 64 characters long. As a consequence: - mesh passwords can't be 64 characters in length - SAE only works with passwords with lengths >8 and <=63 (due to psk limitation). Fix this by always using 'sae_password' with SAE/mesh and applying the PMK differentiation only when PSK is used. Fixes: #11324 Signed-off-by: Leon M. Busch-George <leon@georgemail.eu> [ improve commit description ] Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Diffstat (limited to 'toolchain/kernel-headers')
0 files changed, 0 insertions, 0 deletions