tests: Fix sigma_dut_sae_h2e_rsnxe_mismatch to clear sae_pwe
sae_pwe=1 could be left configured when exiting this test case since sigma_dut does not guarantee the default value to be restored. This could result in test case failures, e.g., in the following sequence: sigma_dut_sae_h2e_rsnxe_mismatch sae_pwe_h2e_only_ap_sta_forcing_loop Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
22319c7fed
commit
78e931e7f9
1 changed files with 1 additions and 0 deletions
|
@ -3591,6 +3591,7 @@ def test_sigma_dut_sae_h2e_rsnxe_mismatch(dev, apdev):
|
||||||
raise Exception("Unexpected connection reported")
|
raise Exception("Unexpected connection reported")
|
||||||
finally:
|
finally:
|
||||||
stop_sigma_dut(sigma)
|
stop_sigma_dut(sigma)
|
||||||
|
dev[0].set("sae_pwe", "0")
|
||||||
|
|
||||||
def test_sigma_dut_ap_sae_h2e_rsnxe_mismatch(dev, apdev, params):
|
def test_sigma_dut_ap_sae_h2e_rsnxe_mismatch(dev, apdev, params):
|
||||||
"""sigma_dut controlled SAE H2E AP misbehavior with RSNXE"""
|
"""sigma_dut controlled SAE H2E AP misbehavior with RSNXE"""
|
||||||
|
|
Loading…
Reference in a new issue