17b7032891
While this is not part of RFC 4137, the way m.check(eapReqData) is implemented in wpa_supplicant allows an EAP method to not update the ignore value even though each such call is really supposed to get a new response. It seems to be possible to hit a sequence where a previous EAP authentication attempt terminates with sm->ignore set from the last m.check() call and the following EAP authentication attempt could fail to go through the expected code path if it does not clear the ignore flag. This is likely only hit in some error cases, though. The hwsim test cases could trigger this with the following sequence: eap_proto_ikev2 ap_wps_m1_oom Signed-off-by: Jouni Malinen <j@w1.fi> |
||
---|---|---|
.. | ||
ap | ||
common | ||
crypto | ||
drivers | ||
eap_common | ||
eap_peer | ||
eap_server | ||
eapol_auth | ||
eapol_supp | ||
fst | ||
l2_packet | ||
p2p | ||
pae | ||
radius | ||
rsn_supp | ||
tls | ||
utils | ||
wps | ||
lib.rules | ||
Makefile |