EAP-MD5: Use conditional success decision
The server may still reject authentication at this point, so better use conditional success decision. This allows the potentially following EAP-Failure message to be processed properly. [Bug 354]
This commit is contained in:
parent
f8bf142175
commit
addb584881
1 changed files with 1 additions and 1 deletions
|
@ -76,7 +76,7 @@ static struct wpabuf * eap_md5_process(struct eap_sm *sm, void *priv,
|
||||||
|
|
||||||
wpa_printf(MSG_DEBUG, "EAP-MD5: Generating Challenge Response");
|
wpa_printf(MSG_DEBUG, "EAP-MD5: Generating Challenge Response");
|
||||||
ret->methodState = METHOD_DONE;
|
ret->methodState = METHOD_DONE;
|
||||||
ret->decision = DECISION_UNCOND_SUCC;
|
ret->decision = DECISION_COND_SUCC;
|
||||||
ret->allowNotifications = TRUE;
|
ret->allowNotifications = TRUE;
|
||||||
|
|
||||||
resp = eap_msg_alloc(EAP_VENDOR_IETF, EAP_TYPE_MD5, 1 + CHAP_MD5_LEN,
|
resp = eap_msg_alloc(EAP_VENDOR_IETF, EAP_TYPE_MD5, 1 + CHAP_MD5_LEN,
|
||||||
|
|
Loading…
Reference in a new issue