On 1/8/20 3:04 PM, Ben Greear wrote:
Hello Jouni, While testing some HS20 (r1) scenarios, we found that associations fail with code 31 (PMF not valid) if AP and STA are configured to not use .11w (PMF).
Ahh, I think I see. I found the hs20_release config option, probably that and other commits around there explains our issue. We'll try forcing the AP back to hs20-release 1 and see if STA can connect without PMF. Thanks, Ben
From what I can tell, the change in this patch is affecting our HS20-r1 setup, not just an HS20-r2 config. Is that expected behaviour? I tried reverting just this patch, but the AP still rejects with the same reason, though with it reverted, the assoc frame did not have the use-pmf bit set. So, AP was rejecting with and without the pmf bit set. AP is recent-ish hostapd on ath9k, and sta is ath9k as well. Thanks, Ben Author: Jouni Malinen <jouni@xxxxxxxxxxxxxx> 2018-12-08 05:46:56 Committer: Jouni Malinen <j@xxxxx> 2018-12-08 07:06:58 Parent: f3784a6b9423a94215dc2ee4fd01b3cf3ed611b8 (HS 2.0: Reject Hotspot 2.0 Rel 2 or newer association without PMF) Child: 842c29c173f3a80ac74e0fa3e57a134e9d301f06 (tests: Hotspot 2.0 connection attempt without PMF) Branches: master, remotes/origin/master Follows: hostap_2_3 Precedes: lf-5.3.9 HS 2.0: Enable PMF automatically for Hotspot 2.0 network profiles Hotspot 2.0 Release 2 requires PMF to be negotiated, so enable this by default in the network profiles created from cred blocks. Signed-off-by: Jouni Malinen <jouni@xxxxxxxxxxxxxx>
_______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
