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")
98 material, they cannot be used with WPA or IEEE 802.1X WEP keying)
120 - minimal size (ca. 50 kB binary, parts of which are already needed for WPA;
133 Linux drivers that support WPA/WPA2 configuration with the generic
145 to work in WPA mode.
148 with Windows NDIS driver for your wlan card supporting WPA.
161 (CFLAGS += -I../madwifi/wpa line in example defconfig).
191 used with IEEE 802.1X (i.e., not WPA) when using ap_scan=0 option in
208 is to add full WPA/WPA2 support to Linux wireless extensions to allow
241 EAP-FAST support is enabled. WPA-PSK mode does not require this or EAPOL/EAP
244 EAP-GTC, EAP-OTP, and EAP-MSCHAPV2 cannot be used alone with WPA, so
254 WPA
268 is called Wi-Fi Protected Access<TM> (WPA). This has now become a
270 by Wi-Fi Alliance. Wi-Fi provides information about WPA at its web
283 WPA is an intermediate solution for the security issues. It uses
290 Keys can be managed using two different mechanisms. WPA can either use
293 servers. Wi-Fi calls these "WPA-Enterprise" and "WPA-Personal",
297 WPA implements a new key handshake (4-Way Handshake and Group Key
310 The design for parts of IEEE 802.11i that were not included in WPA has
313 version of WPA called WPA2. This includes, e.g., support for more
323 wpa_supplicant is an implementation of the WPA Supplicant component,
324 i.e., the part that runs in the client stations. It implements WPA key
325 negotiation with a WPA Authenticator and EAP authentication with
334 Following steps are used when associating with an AP using WPA:
340 - If WPA-EAP: integrated IEEE 802.1X Supplicant completes EAP
343 - If WPA-EAP: master key is received from the IEEE 802.1X Supplicant
344 - If WPA-PSK: wpa_supplicant uses PSK as the master session key
345 - wpa_supplicant completes WPA 4-Way Handshake and Group Key Handshake
578 file, network security level (WPA/WPA2 is preferred), and signal
583 1) WPA-Personal (PSK) as home network and WPA-Enterprise with EAP-TLS as work
594 key_mgmt=WPA-PSK
598 # work network; use EAP-TLS with WPA; allow only CCMP and TKIP ciphers
602 key_mgmt=WPA-EAP
614 2) WPA-RADIUS/EAP-PEAP/MSCHAPv2 with RADIUS servers that use old peaplabel
622 key_mgmt=WPA-EAP
640 key_mgmt=WPA-EAP
650 4) IEEE 802.1X (i.e., no WPA) with dynamic WEP keys (require both unicast and
679 key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
808 status = get current WPA/EAPOL/EAP status
905 WPA. It can be started either from system startup scripts or from
906 pcmcia-cs/cardmgr scripts (when using PC Cards). WPA handshake must be
911 to enable WPA support:
913 Add MODE="Managed" and WPA="y" to the network scheme in
919 if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
927 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.
980 rest of the code (e.g., EAP authentication and WPA handshakes) into an
