iwd/autotests/testSAE/ssidSAE-H2E.conf

hw_mode=g
channel=1
ssid=ssidSAE-H2E

wpa=2
wpa_key_mgmt=SAE
wpa_pairwise=CCMP
sae_password=secret123
sae_password=withidentifier|id=myidentifier
sae_groups=19
ieee80211w=2
sae_pwe=1
auto-t: refactor/fix testSAE The SAE test made some assumptions on certain conditions due to there being no way of checking if those conditions were met Mainly the use of H2E/hunt-and-peck. We assumed that when we told hostapd to use H2E or hunt/peck it would but in reality it was not. Hostapd is apparently not very good at swapping between the two with a simple "reload" command. Once H2E is enabled it appears that it cannot be undone. Similarly the vendor elements seem to carry over from test to test, and sometimes not which causes unintended behavior. To fix this create separate APs for the specific scenario being tested: - Hunt and peck - H2E - Special vendor_element simulating buggy APs Another issue found was that if password identifies are used hostapd automatically chooses H2E which was not intented, at least based on the test names (in reality it wasn't causing any problems). The tests have also been improved to use hostapds "sta_status" command which contains the group number used when authenticating, so now that at least can be verified. 2024-02-27 19:34:03 +01:00			`hw_mode=g`
			`channel=1`
			`ssid=ssidSAE-H2E`

			`wpa=2`
			`wpa_key_mgmt=SAE`
			`wpa_pairwise=CCMP`
			`sae_password=secret123`
			`sae_password=withidentifier\|id=myidentifier`
			`sae_groups=19`
			`ieee80211w=2`
			`sae_pwe=1`