Lines Matching refs:EAP

1 # hostapd user database for integrated EAP server
3 # Each line must contain an identity, EAP method(s), and an optional password
13 # 2 authentication (e.g., within EAP-PEAP). In these cases, an anonymous
19 # EAP-TLS, EAP-PEAP, EAP-TTLS, EAP-FAST, EAP-SIM, and EAP-AKA do not use
21 # EAP-MD5, EAP-MSCHAPV2, EAP-GTC, EAP-PAX, EAP-PSK, and EAP-SAKE require a
23 # EAP-PEAP, EAP-TTLS, and EAP-FAST require Phase 2 configuration.
26 # this are to set anonymous phase 1 identity for EAP-PEAP and EAP-TTLS and to
27 # avoid having to configure every certificate for EAP-TLS authentication. The
32 # main purpose for this is to be able to avoid EAP method negotiation when the
33 # method is using known prefix in identities (e.g., EAP-SIM and EAP-AKA). This
40 # [ver=0] and [ver=1] flags after EAP type PEAP can be used to force PEAP
41 # version based on the Phase 1 identity. Without this flag, the EAP
45 # EAP-TTLS supports both EAP and non-EAP authentication inside the tunnel.
46 # Tunneled EAP methods are configured with standard EAP method name and [2]
47 # flag. Non-EAP methods can be enabled by following method names: TTLS-PAP,
54 # hostapd.conf. For EAP server, this is configured separately for each user
71 # Default to EAP-SIM and EAP-AKA based on fixed identity prefixes
85 # Phase 2 (tunnelled within EAP-PEAP or EAP-TTLS) users
94 # Default to EAP-SIM and EAP-AKA based on fixed identity prefixes in phase 2