Lines Matching refs:SUCCESS
444 SM_STATE(EAP, SUCCESS)
446 SM_ENTRY(EAP, SUCCESS);
460 * to get EAPOL Supplicant backend state machine into SUCCESS state. In
503 * EAP-Success/Failure with lastId + 1 even though RFC 3748 and
505 * Ringmaster v2.1.2.0 would be using lastId + 2 in EAP-Success.
509 * security implications (bit easier to fake EAP-Success/Failure).
514 "identifier field in EAP Success: "
519 wpa_printf(MSG_DEBUG, "EAP: EAP-Success Id mismatch - reqId=%d "
566 * PEAP server not sending EAP-Success in some cases.
574 SM_ENTER(EAP, SUCCESS);
585 SM_ENTER(EAP, SUCCESS);
589 SM_ENTER(EAP, SUCCESS);
613 * around odd LEAP behavior (EAP-Success in the middle of
620 SM_ENTER(EAP, SUCCESS);
1137 wpa_printf(MSG_DEBUG, "EAP: Received EAP-Success");
1286 return "SUCCESS";
1838 * eap_notify_success - Notify EAP state machine about external success trigger
1843 * success state. This is mainly used with security modes that do not use EAP
1856 * eap_notify_lower_layer_success - Notification of lower layer success
1860 * authentication. This is used to recover from dropped EAP-Success messages.
1878 "layer success)");
