Lines Matching full:wpa
0 WPA Supplicant
68 Supported WPA/IEEE 802.11i features:
69 - WPA-PSK ("WPA-Personal")
70 - WPA with EAP (e.g., with RADIUS authentication server) ("WPA-Enterprise")
97 material, they cannot be used with WPA or IEEE 802.1X WEP keying)
119 - minimal size (ca. 50 kB binary, parts of which are already needed for WPA;
132 Linux drivers that support WPA/WPA2 configuration with the generic
144 to work in WPA mode.
147 with Windows NDIS driver for your wlan card supporting WPA.
160 (CFLAGS += -I../madwifi/wpa line in example defconfig).
187 used with IEEE 802.1X (i.e., not WPA) when using ap_scan=0 option in
204 is to add full WPA/WPA2 support to Linux wireless extensions to allow
237 EAP-FAST support is enabled. WPA-PSK mode does not require this or EAPOL/EAP
240 EAP-GTC, EAP-OTP, and EAP-MSCHAPV2 cannot be used alone with WPA, so
250 WPA
264 is called Wi-Fi Protected Access<TM> (WPA). This has now become a
266 by Wi-Fi Alliance. Wi-Fi provides information about WPA at its web
279 WPA is an intermediate solution for the security issues. It uses
286 Keys can be managed using two different mechanisms. WPA can either use
289 servers. Wi-Fi calls these "WPA-Enterprise" and "WPA-Personal",
293 WPA implements a new key handshake (4-Way Handshake and Group Key
306 The design for parts of IEEE 802.11i that were not included in WPA has
309 version of WPA called WPA2. This includes, e.g., support for more
319 wpa_supplicant is an implementation of the WPA Supplicant component,
320 i.e., the part that runs in the client stations. It implements WPA key
321 negotiation with a WPA Authenticator and EAP authentication with
330 Following steps are used when associating with an AP using WPA:
336 - If WPA-EAP: integrated IEEE 802.1X Supplicant completes EAP
339 - If WPA-EAP: master key is received from the IEEE 802.1X Supplicant
340 - If WPA-PSK: wpa_supplicant uses PSK as the master session key
341 - wpa_supplicant completes WPA 4-Way Handshake and Group Key Handshake
572 file, network security level (WPA/WPA2 is preferred), and signal
577 1) WPA-Personal (PSK) as home network and WPA-Enterprise with EAP-TLS as work
588 key_mgmt=WPA-PSK
592 # work network; use EAP-TLS with WPA; allow only CCMP and TKIP ciphers
596 key_mgmt=WPA-EAP
608 2) WPA-RADIUS/EAP-PEAP/MSCHAPv2 with RADIUS servers that use old peaplabel
616 key_mgmt=WPA-EAP
634 key_mgmt=WPA-EAP
644 4) IEEE 802.1X (i.e., no WPA) with dynamic WEP keys (require both unicast and
673 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
802 status = get current WPA/EAPOL/EAP status
899 WPA. It can be started either from system startup scripts or from
900 pcmcia-cs/cardmgr scripts (when using PC Cards). WPA handshake must be
909 to enable WPA support:
911 Add MODE="Managed" and WPA="y" to the network scheme in
917 if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
925 if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
959 wpa_cli -iwlan0 set_network 0 key_mgmt WPA-PSK
963 wpa_cli -iwlan0 set_network 0 proto WPA
967 # with the WPA-PSK network using SSID test.
