Lines Matching refs:EAP
2 \page eap_server_module EAP server implementation
4 Extensible Authentication Protocol (EAP) is an authentication framework
5 defined in RFC 3748. hostapd uses a separate code module for EAP server
8 it to be usable in other programs. The design of the EAP
12 understanding the EAP server implementation in hostapd.
14 Some of the terminology used in EAP state machine is referring to
16 layer being IEEE 802.1X if EAP module is built for other programs than
21 \section adding_eap_methods Adding EAP methods
23 Each EAP method is implemented as a separate module, usually as one C
24 file named eap_server_<name of the method>.c, e.g., \ref eap_server_md5.c. All EAP
26 method specific functions. This allows new EAP methods to be added
27 without modifying the core EAP state machine implementation.
29 New EAP methods need to be registered by adding them into the build
30 (Makefile) and the EAP method registration list in the
31 \ref eap_server_register_methods() function of \ref eap_server_methods.c. Each EAP
36 EAP methods must implement the interface defined in \ref eap_i.h. struct
37 \ref eap_method defines the needed function pointers that each EAP method
38 must provide. In addition, the EAP type and name are registered using
41 It is recommended that the EAP methods would use generic helper
45 functions make it easier to change between expanded and legacy EAP
48 When adding an EAP method that uses a vendor specific EAP type
52 expanded types by registering a legacy EAP method for type 254. See
53 \ref eap_server_vendor_test.c for an example of an EAP method implementation that