Lines Matching refs:SUCCESS
667 min_len = 0; /* LEAP uses EAP-Success without payload */
821 SM_STATE(EAP, SUCCESS)
823 SM_ENTRY(EAP, SUCCESS);
837 * to get EAPOL Supplicant backend state machine into SUCCESS state. In
882 * EAP-Success/Failure with lastId + 1 even though RFC 3748 and
884 * Ringmaster v2.1.2.0 would be using lastId + 2 in EAP-Success.
888 * security implications (bit easier to fake EAP-Success/Failure).
893 "identifier field in EAP Success: "
898 wpa_printf(MSG_DEBUG, "EAP: EAP-Success Id mismatch - reqId=%d "
913 * not sending EAP-Success in some cases.
921 SM_ENTER(EAP, SUCCESS);
932 SM_ENTER(EAP, SUCCESS);
936 SM_ENTER(EAP, SUCCESS);
981 * odd LEAP behavior (EAP-Success in the middle of authentication and
987 SM_ENTER(EAP, SUCCESS);
990 SM_ENTER(EAP, SUCCESS); /* EAP-Success prior any EAP method */
998 SM_ENTER(EAP, SUCCESS); /* EAP-Success after Identity */
1839 wpa_printf(MSG_DEBUG, "EAP: Received EAP-Success");
1840 eap_notify_status(sm, "completion", "success");
1871 "success");
2078 return "SUCCESS";
2714 * eap_notify_success - Notify EAP state machine about external success trigger
2719 * success state. This is mainly used with security modes that do not use EAP
2732 * eap_notify_lower_layer_success - Notification of lower layer success
2736 * authentication. This is used to recover from dropped EAP-Success messages.
2754 "layer success)");
