Lines Matching refs:in
5 defined in RFC 3748. wpa_supplicant uses a separate code module for EAP
7 of direct function calls (mainly, to debug/event functions) in order for
8 it to be usable in other programs. The design of the EAP
10 defined in this RFC and so is the interface between the peer state
12 understanding the EAP peer implementation in wpa_supplicant.
14 Some of the terminology used in EAP state machine is referring to
18 lower layer as defined in RFC 4137.
30 (Makefile) and the EAP method registration list in the
32 method should use a build-time configuration option, e.g., EAP_TLS, in
34 in the build.
36 EAP methods must implement the interface defined in \ref eap_i.h. struct
49 (Expanded Type as defined in RFC 3748, Chapter 5.7), the new method
67 same for EAP server. \ref eap_example.c is an example that ties in both the
73 In practice, server and peer functionalities would likely reside in
75 devices based on an external protocol. For example, in IEEE 802.11
78 mechanism that transmits EAP messages as defined in IEEE 802.16e.
80 The EAP library links in number of helper functions from \ref src/utils and
82 be desirable to replace the debug output code in \ref src/utils/wpa_debug.c
84 functions there in a way that better fits in with the main