wok-current diff wpa_supplicant/stuff/etc/wpa_supplicant.conf @ rev 9926
gphoto2: Replaced libtool with libltdl in depends.
author | Christopher Rogers <slaxemulator@gmail.com> |
---|---|
date | Tue May 17 17:22:40 2011 +0000 (2011-05-17) |
parents | |
children | 01ad1e61b761 |
line diff
1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 1.2 +++ b/wpa_supplicant/stuff/etc/wpa_supplicant.conf Tue May 17 17:22:40 2011 +0000 1.3 @@ -0,0 +1,754 @@ 1.4 +##### Example wpa_supplicant configuration file ############################### 1.5 +# 1.6 +# This file describes configuration file format and lists all available option. 1.7 +# Please also take a look at simpler configuration examples in 'examples' 1.8 +# subdirectory. 1.9 +# 1.10 +# Empty lines and lines starting with # are ignored 1.11 + 1.12 +# NOTE! This file may contain password information and should probably be made 1.13 +# readable only by root user on multiuser systems. 1.14 + 1.15 +# Note: All file paths in this configuration file should use full (absolute, 1.16 +# not relative to working directory) path in order to allow working directory 1.17 +# to be changed. This can happen if wpa_supplicant is run in the background. 1.18 + 1.19 +# Whether to allow wpa_supplicant to update (overwrite) configuration 1.20 +# 1.21 +# This option can be used to allow wpa_supplicant to overwrite configuration 1.22 +# file whenever configuration is changed (e.g., new network block is added with 1.23 +# wpa_cli or wpa_gui, or a password is changed). This is required for 1.24 +# wpa_cli/wpa_gui to be able to store the configuration changes permanently. 1.25 +# Please note that overwriting configuration file will remove the comments from 1.26 +# it. 1.27 +#update_config=1 1.28 + 1.29 +# global configuration (shared by all network blocks) 1.30 +# 1.31 +# Parameters for the control interface. If this is specified, wpa_supplicant 1.32 +# will open a control interface that is available for external programs to 1.33 +# manage wpa_supplicant. The meaning of this string depends on which control 1.34 +# interface mechanism is used. For all cases, the existance of this parameter 1.35 +# in configuration is used to determine whether the control interface is 1.36 +# enabled. 1.37 +# 1.38 +# For UNIX domain sockets (default on Linux and BSD): This is a directory that 1.39 +# will be created for UNIX domain sockets for listening to requests from 1.40 +# external programs (CLI/GUI, etc.) for status information and configuration. 1.41 +# The socket file will be named based on the interface name, so multiple 1.42 +# wpa_supplicant processes can be run at the same time if more than one 1.43 +# interface is used. 1.44 +# /var/run/wpa_supplicant is the recommended directory for sockets and by 1.45 +# default, wpa_cli will use it when trying to connect with wpa_supplicant. 1.46 +# 1.47 +# Access control for the control interface can be configured by setting the 1.48 +# directory to allow only members of a group to use sockets. This way, it is 1.49 +# possible to run wpa_supplicant as root (since it needs to change network 1.50 +# configuration and open raw sockets) and still allow GUI/CLI components to be 1.51 +# run as non-root users. However, since the control interface can be used to 1.52 +# change the network configuration, this access needs to be protected in many 1.53 +# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you 1.54 +# want to allow non-root users to use the control interface, add a new group 1.55 +# and change this value to match with that group. Add users that should have 1.56 +# control interface access to this group. If this variable is commented out or 1.57 +# not included in the configuration file, group will not be changed from the 1.58 +# value it got by default when the directory or socket was created. 1.59 +# 1.60 +# When configuring both the directory and group, use following format: 1.61 +# DIR=/var/run/wpa_supplicant GROUP=wheel 1.62 +# DIR=/var/run/wpa_supplicant GROUP=0 1.63 +# (group can be either group name or gid) 1.64 +# 1.65 +# For UDP connections (default on Windows): The value will be ignored. This 1.66 +# variable is just used to select that the control interface is to be created. 1.67 +# The value can be set to, e.g., udp (ctrl_interface=udp) 1.68 +# 1.69 +# For Windows Named Pipe: This value can be used to set the security descriptor 1.70 +# for controlling access to the control interface. Security descriptor can be 1.71 +# set using Security Descriptor String Format (see http://msdn.microsoft.com/ 1.72 +# library/default.asp?url=/library/en-us/secauthz/security/ 1.73 +# security_descriptor_string_format.asp). The descriptor string needs to be 1.74 +# prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty 1.75 +# DACL (which will reject all connections). See README-Windows.txt for more 1.76 +# information about SDDL string format. 1.77 +# 1.78 +ctrl_interface=/var/run/wpa_supplicant 1.79 + 1.80 +# Ensure that only root can read the WPA configuration 1.81 +ctrl_interface_group=0 1.82 + 1.83 + 1.84 +# IEEE 802.1X/EAPOL version 1.85 +# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines 1.86 +# EAPOL version 2. However, there are many APs that do not handle the new 1.87 +# version number correctly (they seem to drop the frames completely). In order 1.88 +# to make wpa_supplicant interoperate with these APs, the version number is set 1.89 +# to 1 by default. This configuration value can be used to set it to the new 1.90 +# version (2). 1.91 +eapol_version=1 1.92 + 1.93 +# AP scanning/selection 1.94 +# By default, wpa_supplicant requests driver to perform AP scanning and then 1.95 +# uses the scan results to select a suitable AP. Another alternative is to 1.96 +# allow the driver to take care of AP scanning and selection and use 1.97 +# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association 1.98 +# information from the driver. 1.99 +# 1: wpa_supplicant initiates scanning and AP selection 1.100 +# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association 1.101 +# parameters (e.g., WPA IE generation); this mode can also be used with 1.102 +# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with 1.103 +# APs (i.e., external program needs to control association). This mode must 1.104 +# also be used when using wired Ethernet drivers. 1.105 +# 2: like 0, but associate with APs using security policy and SSID (but not 1.106 +# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to 1.107 +# enable operation with hidden SSIDs and optimized roaming; in this mode, 1.108 +# the network blocks in the configuration file are tried one by one until 1.109 +# the driver reports successful association; each network block should have 1.110 +# explicit security policy (i.e., only one option in the lists) for 1.111 +# key_mgmt, pairwise, group, proto variables 1.112 +ap_scan=1 1.113 + 1.114 +# EAP fast re-authentication 1.115 +# By default, fast re-authentication is enabled for all EAP methods that 1.116 +# support it. This variable can be used to disable fast re-authentication. 1.117 +# Normally, there is no need to disable this. 1.118 +fast_reauth=1 1.119 + 1.120 +# OpenSSL Engine support 1.121 +# These options can be used to load OpenSSL engines. 1.122 +# The two engines that are supported currently are shown below: 1.123 +# They are both from the opensc project (http://www.opensc.org/) 1.124 +# By default no engines are loaded. 1.125 +# make the opensc engine available 1.126 +#opensc_engine_path=/usr/lib/opensc/engine_opensc.so 1.127 +# make the pkcs11 engine available 1.128 +#pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so 1.129 +# configure the path to the pkcs11 module required by the pkcs11 engine 1.130 +#pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so 1.131 + 1.132 +# Dynamic EAP methods 1.133 +# If EAP methods were built dynamically as shared object files, they need to be 1.134 +# loaded here before being used in the network blocks. By default, EAP methods 1.135 +# are included statically in the build, so these lines are not needed 1.136 +#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so 1.137 +#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so 1.138 + 1.139 +# Driver interface parameters 1.140 +# This field can be used to configure arbitrary driver interace parameters. The 1.141 +# format is specific to the selected driver interface. This field is not used 1.142 +# in most cases. 1.143 +#driver_param="field=value" 1.144 + 1.145 +# Maximum lifetime for PMKSA in seconds; default 43200 1.146 +#dot11RSNAConfigPMKLifetime=43200 1.147 +# Threshold for reauthentication (percentage of PMK lifetime); default 70 1.148 +#dot11RSNAConfigPMKReauthThreshold=70 1.149 +# Timeout for security association negotiation in seconds; default 60 1.150 +#dot11RSNAConfigSATimeout=60 1.151 + 1.152 +# network block 1.153 +# 1.154 +# Each network (usually AP's sharing the same SSID) is configured as a separate 1.155 +# block in this configuration file. The network blocks are in preference order 1.156 +# (the first match is used). 1.157 +# 1.158 +# network block fields: 1.159 +# 1.160 +# disabled: 1.161 +# 0 = this network can be used (default) 1.162 +# 1 = this network block is disabled (can be enabled through ctrl_iface, 1.163 +# e.g., with wpa_cli or wpa_gui) 1.164 +# 1.165 +# id_str: Network identifier string for external scripts. This value is passed 1.166 +# to external action script through wpa_cli as WPA_ID_STR environment 1.167 +# variable to make it easier to do network specific configuration. 1.168 +# 1.169 +# ssid: SSID (mandatory); either as an ASCII string with double quotation or 1.170 +# as hex string; network name 1.171 +# 1.172 +# scan_ssid: 1.173 +# 0 = do not scan this SSID with specific Probe Request frames (default) 1.174 +# 1 = scan with SSID-specific Probe Request frames (this can be used to 1.175 +# find APs that do not accept broadcast SSID or use multiple SSIDs; 1.176 +# this will add latency to scanning, so enable this only when needed) 1.177 +# 1.178 +# bssid: BSSID (optional); if set, this network block is used only when 1.179 +# associating with the AP using the configured BSSID 1.180 +# 1.181 +# priority: priority group (integer) 1.182 +# By default, all networks will get same priority group (0). If some of the 1.183 +# networks are more desirable, this field can be used to change the order in 1.184 +# which wpa_supplicant goes through the networks when selecting a BSS. The 1.185 +# priority groups will be iterated in decreasing priority (i.e., the larger the 1.186 +# priority value, the sooner the network is matched against the scan results). 1.187 +# Within each priority group, networks will be selected based on security 1.188 +# policy, signal strength, etc. 1.189 +# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not 1.190 +# using this priority to select the order for scanning. Instead, they try the 1.191 +# networks in the order that used in the configuration file. 1.192 +# 1.193 +# mode: IEEE 802.11 operation mode 1.194 +# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default) 1.195 +# 1 = IBSS (ad-hoc, peer-to-peer) 1.196 +# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP) 1.197 +# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has 1.198 +# to be set to 2 for IBSS. WPA-None requires following network block options: 1.199 +# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not 1.200 +# both), and psk must also be set. 1.201 +# 1.202 +# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g., 1.203 +# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial 1.204 +# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode. 1.205 +# In addition, this value is only used by the station that creates the IBSS. If 1.206 +# an IBSS network with the configured SSID is already present, the frequency of 1.207 +# the network will be used instead of this configured value. 1.208 +# 1.209 +# proto: list of accepted protocols 1.210 +# WPA = WPA/IEEE 802.11i/D3.0 1.211 +# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN) 1.212 +# If not set, this defaults to: WPA RSN 1.213 +# 1.214 +# key_mgmt: list of accepted authenticated key management protocols 1.215 +# WPA-PSK = WPA pre-shared key (this requires 'psk' field) 1.216 +# WPA-EAP = WPA using EAP authentication (this can use an external 1.217 +# program, e.g., Xsupplicant, for IEEE 802.1X EAP Authentication 1.218 +# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically 1.219 +# generated WEP keys 1.220 +# NONE = WPA is not used; plaintext or static WEP could be used 1.221 +# If not set, this defaults to: WPA-PSK WPA-EAP 1.222 +# 1.223 +# auth_alg: list of allowed IEEE 802.11 authentication algorithms 1.224 +# OPEN = Open System authentication (required for WPA/WPA2) 1.225 +# SHARED = Shared Key authentication (requires static WEP keys) 1.226 +# LEAP = LEAP/Network EAP (only used with LEAP) 1.227 +# If not set, automatic selection is used (Open System with LEAP enabled if 1.228 +# LEAP is allowed as one of the EAP methods). 1.229 +# 1.230 +# pairwise: list of accepted pairwise (unicast) ciphers for WPA 1.231 +# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 1.232 +# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 1.233 +# NONE = Use only Group Keys (deprecated, should not be included if APs support 1.234 +# pairwise keys) 1.235 +# If not set, this defaults to: CCMP TKIP 1.236 +# 1.237 +# group: list of accepted group (broadcast/multicast) ciphers for WPA 1.238 +# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0] 1.239 +# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0] 1.240 +# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key 1.241 +# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11] 1.242 +# If not set, this defaults to: CCMP TKIP WEP104 WEP40 1.243 +# 1.244 +# psk: WPA preshared key; 256-bit pre-shared key 1.245 +# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e., 1.246 +# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be 1.247 +# generated using the passphrase and SSID). ASCII passphrase must be between 1.248 +# 8 and 63 characters (inclusive). 1.249 +# This field is not needed, if WPA-EAP is used. 1.250 +# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys 1.251 +# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant 1.252 +# startup and reconfiguration time can be optimized by generating the PSK only 1.253 +# only when the passphrase or SSID has actually changed. 1.254 +# 1.255 +# eapol_flags: IEEE 802.1X/EAPOL options (bit field) 1.256 +# Dynamic WEP key required for non-WPA mode 1.257 +# bit0 (1): require dynamically generated unicast WEP key 1.258 +# bit1 (2): require dynamically generated broadcast WEP key 1.259 +# (3 = require both keys; default) 1.260 +# Note: When using wired authentication, eapol_flags must be set to 0 for the 1.261 +# authentication to be completed successfully. 1.262 +# 1.263 +# mixed_cell: This option can be used to configure whether so called mixed 1.264 +# cells, i.e., networks that use both plaintext and encryption in the same 1.265 +# SSID, are allowed when selecting a BSS form scan results. 1.266 +# 0 = disabled (default) 1.267 +# 1 = enabled 1.268 +# 1.269 +# proactive_key_caching: 1.270 +# Enable/disable opportunistic PMKSA caching for WPA2. 1.271 +# 0 = disabled (default) 1.272 +# 1 = enabled 1.273 +# 1.274 +# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or 1.275 +# hex without quotation, e.g., 0102030405) 1.276 +# wep_tx_keyidx: Default WEP key index (TX) (0..3) 1.277 +# 1.278 +# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is 1.279 +# allowed. This is only used with RSN/WPA2. 1.280 +# 0 = disabled (default) 1.281 +# 1 = enabled 1.282 +#peerkey=1 1.283 +# 1.284 +# Following fields are only used with internal EAP implementation. 1.285 +# eap: space-separated list of accepted EAP methods 1.286 +# MD5 = EAP-MD5 (unsecure and does not generate keying material -> 1.287 +# cannot be used with WPA; to be used as a Phase 2 method 1.288 +# with EAP-PEAP or EAP-TTLS) 1.289 +# MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used 1.290 +# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 1.291 +# OTP = EAP-OTP (cannot be used separately with WPA; to be used 1.292 +# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 1.293 +# GTC = EAP-GTC (cannot be used separately with WPA; to be used 1.294 +# as a Phase 2 method with EAP-PEAP or EAP-TTLS) 1.295 +# TLS = EAP-TLS (client and server certificate) 1.296 +# PEAP = EAP-PEAP (with tunnelled EAP authentication) 1.297 +# TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2 1.298 +# authentication) 1.299 +# If not set, all compiled in methods are allowed. 1.300 +# 1.301 +# identity: Identity string for EAP 1.302 +# anonymous_identity: Anonymous identity string for EAP (to be used as the 1.303 +# unencrypted identity with EAP types that support different tunnelled 1.304 +# identity, e.g., EAP-TTLS) 1.305 +# password: Password string for EAP 1.306 +# ca_cert: File path to CA certificate file (PEM/DER). This file can have one 1.307 +# or more trusted CA certificates. If ca_cert and ca_path are not 1.308 +# included, server certificate will not be verified. This is insecure and 1.309 +# a trusted CA certificate should always be configured when using 1.310 +# EAP-TLS/TTLS/PEAP. Full path should be used since working directory may 1.311 +# change when wpa_supplicant is run in the background. 1.312 +# On Windows, trusted CA certificates can be loaded from the system 1.313 +# certificate store by setting this to cert_store://<name>, e.g., 1.314 +# ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT". 1.315 +# Note that when running wpa_supplicant as an application, the user 1.316 +# certificate store (My user account) is used, whereas computer store 1.317 +# (Computer account) is used when running wpasvc as a service. 1.318 +# ca_path: Directory path for CA certificate files (PEM). This path may 1.319 +# contain multiple CA certificates in OpenSSL format. Common use for this 1.320 +# is to point to system trusted CA list which is often installed into 1.321 +# directory like /etc/ssl/certs. If configured, these certificates are 1.322 +# added to the list of trusted CAs. ca_cert may also be included in that 1.323 +# case, but it is not required. 1.324 +# client_cert: File path to client certificate file (PEM/DER) 1.325 +# Full path should be used since working directory may change when 1.326 +# wpa_supplicant is run in the background. 1.327 +# Alternatively, a named configuration blob can be used by setting this 1.328 +# to blob://<blob name>. 1.329 +# private_key: File path to client private key file (PEM/DER/PFX) 1.330 +# When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 1.331 +# commented out. Both the private key and certificate will be read from 1.332 +# the PKCS#12 file in this case. Full path should be used since working 1.333 +# directory may change when wpa_supplicant is run in the background. 1.334 +# Windows certificate store can be used by leaving client_cert out and 1.335 +# configuring private_key in one of the following formats: 1.336 +# cert://substring_to_match 1.337 +# hash://certificate_thumbprint_in_hex 1.338 +# for example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 1.339 +# Note that when running wpa_supplicant as an application, the user 1.340 +# certificate store (My user account) is used, whereas computer store 1.341 +# (Computer account) is used when running wpasvc as a service. 1.342 +# Alternatively, a named configuration blob can be used by setting this 1.343 +# to blob://<blob name>. 1.344 +# private_key_passwd: Password for private key file (if left out, this will be 1.345 +# asked through control interface) 1.346 +# dh_file: File path to DH/DSA parameters file (in PEM format) 1.347 +# This is an optional configuration file for setting parameters for an 1.348 +# ephemeral DH key exchange. In most cases, the default RSA 1.349 +# authentication does not use this configuration. However, it is possible 1.350 +# setup RSA to use ephemeral DH key exchange. In addition, ciphers with 1.351 +# DSA keys always use ephemeral DH keys. This can be used to achieve 1.352 +# forward secrecy. If the file is in DSA parameters format, it will be 1.353 +# automatically converted into DH params. 1.354 +# subject_match: Substring to be matched against the subject of the 1.355 +# authentication server certificate. If this string is set, the server 1.356 +# sertificate is only accepted if it contains this string in the subject. 1.357 +# The subject string is in following format: 1.358 +# /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com 1.359 +# altsubject_match: Semicolon separated string of entries to be matched against 1.360 +# the alternative subject name of the authentication server certificate. 1.361 +# If this string is set, the server sertificate is only accepted if it 1.362 +# contains one of the entries in an alternative subject name extension. 1.363 +# altSubjectName string is in following format: TYPE:VALUE 1.364 +# Example: EMAIL:server@example.com 1.365 +# Example: DNS:server.example.com;DNS:server2.example.com 1.366 +# Following types are supported: EMAIL, DNS, URI 1.367 +# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters 1.368 +# (string with field-value pairs, e.g., "peapver=0" or 1.369 +# "peapver=1 peaplabel=1") 1.370 +# 'peapver' can be used to force which PEAP version (0 or 1) is used. 1.371 +# 'peaplabel=1' can be used to force new label, "client PEAP encryption", 1.372 +# to be used during key derivation when PEAPv1 or newer. Most existing 1.373 +# PEAPv1 implementation seem to be using the old label, "client EAP 1.374 +# encryption", and wpa_supplicant is now using that as the default value. 1.375 +# Some servers, e.g., Radiator, may require peaplabel=1 configuration to 1.376 +# interoperate with PEAPv1; see eap_testing.txt for more details. 1.377 +# 'peap_outer_success=0' can be used to terminate PEAP authentication on 1.378 +# tunneled EAP-Success. This is required with some RADIUS servers that 1.379 +# implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g., 1.380 +# Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode) 1.381 +# include_tls_length=1 can be used to force wpa_supplicant to include 1.382 +# TLS Message Length field in all TLS messages even if they are not 1.383 +# fragmented. 1.384 +# sim_min_num_chal=3 can be used to configure EAP-SIM to require three 1.385 +# challenges (by default, it accepts 2 or 3) 1.386 +# phase2: Phase2 (inner authentication with TLS tunnel) parameters 1.387 +# (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or 1.388 +# "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS) 1.389 +# Following certificate/private key fields are used in inner Phase2 1.390 +# authentication when using EAP-TTLS or EAP-PEAP. 1.391 +# ca_cert2: File path to CA certificate file. This file can have one or more 1.392 +# trusted CA certificates. If ca_cert2 and ca_path2 are not included, 1.393 +# server certificate will not be verified. This is insecure and a trusted 1.394 +# CA certificate should always be configured. 1.395 +# ca_path2: Directory path for CA certificate files (PEM) 1.396 +# client_cert2: File path to client certificate file 1.397 +# private_key2: File path to client private key file 1.398 +# private_key2_passwd: Password for private key file 1.399 +# dh_file2: File path to DH/DSA parameters file (in PEM format) 1.400 +# subject_match2: Substring to be matched against the subject of the 1.401 +# authentication server certificate. 1.402 +# altsubject_match2: Substring to be matched against the alternative subject 1.403 +# name of the authentication server certificate. 1.404 +# 1.405 +# fragment_size: Maximum EAP fragment size in bytes (default 1398). 1.406 +# This value limits the fragment size for EAP methods that support 1.407 +# fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set 1.408 +# small enough to make the EAP messages fit in MTU of the network 1.409 +# interface used for EAPOL. The default value is suitable for most 1.410 +# cases. 1.411 +# 1.412 +# EAP-PSK variables: 1.413 +# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format 1.414 +# nai: user NAI 1.415 +# 1.416 +# EAP-PAX variables: 1.417 +# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format 1.418 +# 1.419 +# EAP-SAKE variables: 1.420 +# eappsk: 32-byte (256-bit, 64 hex digits) pre-shared key in hex format 1.421 +# (this is concatenation of Root-Secret-A and Root-Secret-B) 1.422 +# nai: user NAI (PEERID) 1.423 +# 1.424 +# EAP-GPSK variables: 1.425 +# eappsk: Pre-shared key in hex format (at least 128 bits, i.e., 32 hex digits) 1.426 +# nai: user NAI (ID_Client) 1.427 +# 1.428 +# EAP-FAST variables: 1.429 +# pac_file: File path for the PAC entries. wpa_supplicant will need to be able 1.430 +# to create this file and write updates to it when PAC is being 1.431 +# provisioned or refreshed. Full path to the file should be used since 1.432 +# working directory may change when wpa_supplicant is run in the 1.433 +# background. Alternatively, a named configuration blob can be used by 1.434 +# setting this to blob://<blob name> 1.435 +# phase1: fast_provisioning=1 option enables in-line provisioning of EAP-FAST 1.436 +# credentials (PAC) 1.437 +# 1.438 +# wpa_supplicant supports number of "EAP workarounds" to work around 1.439 +# interoperability issues with incorrectly behaving authentication servers. 1.440 +# These are enabled by default because some of the issues are present in large 1.441 +# number of authentication servers. Strict EAP conformance mode can be 1.442 +# configured by disabling workarounds with eap_workaround=0. 1.443 + 1.444 +# Example blocks: 1.445 + 1.446 +# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers 1.447 +#network={ 1.448 +# ssid="simple" 1.449 +# psk="very secret passphrase" 1.450 +# priority=5 1.451 +#} 1.452 + 1.453 +# Same as previous, but request SSID-specific scanning (for APs that reject 1.454 +# broadcast SSID) 1.455 +#network={ 1.456 +# ssid="second ssid" 1.457 +# scan_ssid=1 1.458 +# psk="very secret passphrase" 1.459 +# priority=2 1.460 +#} 1.461 + 1.462 +# Only WPA-PSK is used. Any valid cipher combination is accepted. 1.463 +#network={ 1.464 +# ssid="example" 1.465 +# proto=WPA 1.466 +# key_mgmt=WPA-PSK 1.467 +# pairwise=CCMP TKIP 1.468 +# group=CCMP TKIP WEP104 WEP40 1.469 +# psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 1.470 +# priority=2 1.471 +#} 1.472 + 1.473 +# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104 1.474 +# or WEP40 as the group cipher will not be accepted. 1.475 +#network={ 1.476 +# ssid="example" 1.477 +# proto=RSN 1.478 +# key_mgmt=WPA-EAP 1.479 +# pairwise=CCMP TKIP 1.480 +# group=CCMP TKIP 1.481 +# eap=TLS 1.482 +# identity="user@example.com" 1.483 +# ca_cert="/etc/cert/ca.pem" 1.484 +# client_cert="/etc/cert/user.pem" 1.485 +# private_key="/etc/cert/user.prv" 1.486 +# private_key_passwd="password" 1.487 +# priority=1 1.488 +#} 1.489 + 1.490 +# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel 1.491 +# (e.g., Radiator) 1.492 +#network={ 1.493 +# ssid="example" 1.494 +# key_mgmt=WPA-EAP 1.495 +# eap=PEAP 1.496 +# identity="user@example.com" 1.497 +# password="foobar" 1.498 +# ca_cert="/etc/cert/ca.pem" 1.499 +# phase1="peaplabel=1" 1.500 +# phase2="auth=MSCHAPV2" 1.501 +# priority=10 1.502 +#} 1.503 + 1.504 +# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the 1.505 +# unencrypted use. Real identity is sent only within an encrypted TLS tunnel. 1.506 +#network={ 1.507 +# ssid="example" 1.508 +# key_mgmt=WPA-EAP 1.509 +# eap=TTLS 1.510 +# identity="user@example.com" 1.511 +# anonymous_identity="anonymous@example.com" 1.512 +# password="foobar" 1.513 +# ca_cert="/etc/cert/ca.pem" 1.514 +# priority=2 1.515 +#} 1.516 + 1.517 +# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted 1.518 +# use. Real identity is sent only within an encrypted TLS tunnel. 1.519 +#network={ 1.520 +# ssid="example" 1.521 +# key_mgmt=WPA-EAP 1.522 +# eap=TTLS 1.523 +# identity="user@example.com" 1.524 +# anonymous_identity="anonymous@example.com" 1.525 +# password="foobar" 1.526 +# ca_cert="/etc/cert/ca.pem" 1.527 +# phase2="auth=MSCHAPV2" 1.528 +#} 1.529 + 1.530 +# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner 1.531 +# authentication. 1.532 +#network={ 1.533 +# ssid="example" 1.534 +# key_mgmt=WPA-EAP 1.535 +# eap=TTLS 1.536 + # Phase1 / outer authentication 1.537 +# anonymous_identity="anonymous@example.com" 1.538 +# ca_cert="/etc/cert/ca.pem" 1.539 + # Phase 2 / inner authentication 1.540 +# phase2="autheap=TLS" 1.541 +# ca_cert2="/etc/cert/ca2.pem" 1.542 +# client_cert2="/etc/cer/user.pem" 1.543 +# private_key2="/etc/cer/user.prv" 1.544 +# private_key2_passwd="password" 1.545 +# priority=2 1.546 +#} 1.547 + 1.548 +# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and 1.549 +# group cipher. 1.550 +#network={ 1.551 +# ssid="example" 1.552 +# bssid=00:11:22:33:44:55 1.553 +# proto=WPA RSN 1.554 +# key_mgmt=WPA-PSK WPA-EAP 1.555 +# pairwise=CCMP 1.556 +# group=CCMP 1.557 +# psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb 1.558 +#} 1.559 + 1.560 +# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP 1.561 +# and all valid ciphers. 1.562 +#network={ 1.563 +# ssid=00010203 1.564 +# psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f 1.565 +#} 1.566 + 1.567 + 1.568 +# EAP-SIM with a GSM SIM or USIM 1.569 +#network={ 1.570 +# ssid="eap-sim-test" 1.571 +# key_mgmt=WPA-EAP 1.572 +# eap=SIM 1.573 +# pin="1234" 1.574 +# pcsc="" 1.575 +#} 1.576 + 1.577 + 1.578 +# EAP-PSK 1.579 +#network={ 1.580 +# ssid="eap-psk-test" 1.581 +# key_mgmt=WPA-EAP 1.582 +# eap=PSK 1.583 +# identity="eap_psk_user" 1.584 +# eappsk=06b4be19da289f475aa46a33cb793029 1.585 +# nai="eap_psk_user@example.com" 1.586 +#} 1.587 + 1.588 + 1.589 +# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using 1.590 +# EAP-TLS for authentication and key generation; require both unicast and 1.591 +# broadcast WEP keys. 1.592 +#network={ 1.593 +# ssid="1x-test" 1.594 +# key_mgmt=IEEE8021X 1.595 +# eap=TLS 1.596 +# identity="user@example.com" 1.597 +# ca_cert="/etc/cert/ca.pem" 1.598 +# client_cert="/etc/cert/user.pem" 1.599 +# private_key="/etc/cert/user.prv" 1.600 +# private_key_passwd="password" 1.601 +# eapol_flags=3 1.602 +#} 1.603 + 1.604 + 1.605 +# LEAP with dynamic WEP keys 1.606 +#network={ 1.607 +# ssid="leap-example" 1.608 +# key_mgmt=IEEE8021X 1.609 +# eap=LEAP 1.610 +# identity="user" 1.611 +# password="foobar" 1.612 +#} 1.613 + 1.614 +# EAP-FAST with WPA (WPA or WPA2) 1.615 +#network={ 1.616 +# ssid="eap-fast-test" 1.617 +# key_mgmt=WPA-EAP 1.618 +# eap=FAST 1.619 +# anonymous_identity="FAST-000102030405" 1.620 +# identity="username" 1.621 +# password="password" 1.622 +# phase1="fast_provisioning=1" 1.623 +# pac_file="/etc/wpa_supplicant.eap-fast-pac" 1.624 +#} 1.625 + 1.626 +#network={ 1.627 +# ssid="eap-fast-test" 1.628 +# key_mgmt=WPA-EAP 1.629 +# eap=FAST 1.630 +# anonymous_identity="FAST-000102030405" 1.631 +# identity="username" 1.632 +# password="password" 1.633 +# phase1="fast_provisioning=1" 1.634 +# pac_file="blob://eap-fast-pac" 1.635 +#} 1.636 + 1.637 +# Plaintext connection (no WPA, no IEEE 802.1X) 1.638 +#network={ 1.639 +# ssid="plaintext-test" 1.640 +# key_mgmt=NONE 1.641 +#} 1.642 + 1.643 + 1.644 +# Shared WEP key connection (no WPA, no IEEE 802.1X) 1.645 +#network={ 1.646 +# ssid="static-wep-test" 1.647 +# key_mgmt=NONE 1.648 +# wep_key0="abcde" 1.649 +# wep_key1=0102030405 1.650 +# wep_key2="1234567890123" 1.651 +# wep_tx_keyidx=0 1.652 +# priority=5 1.653 +#} 1.654 + 1.655 + 1.656 +# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key 1.657 +# IEEE 802.11 authentication 1.658 +#network={ 1.659 +# ssid="static-wep-test2" 1.660 +# key_mgmt=NONE 1.661 +# wep_key0="abcde" 1.662 +# wep_key1=0102030405 1.663 +# wep_key2="1234567890123" 1.664 +# wep_tx_keyidx=0 1.665 +# priority=5 1.666 +# auth_alg=SHARED 1.667 +#} 1.668 + 1.669 + 1.670 +# IBSS/ad-hoc network with WPA-None/TKIP. 1.671 +#network={ 1.672 +# ssid="test adhoc" 1.673 +# mode=1 1.674 +# frequency=2412 1.675 +# proto=WPA 1.676 +# key_mgmt=WPA-NONE 1.677 +# pairwise=NONE 1.678 +# group=TKIP 1.679 +# psk="secret passphrase" 1.680 +#} 1.681 + 1.682 + 1.683 +# Catch all example that allows more or less all configuration modes 1.684 +#network={ 1.685 +# ssid="example" 1.686 +# scan_ssid=1 1.687 +# key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE 1.688 +# pairwise=CCMP TKIP 1.689 +# group=CCMP TKIP WEP104 WEP40 1.690 +# psk="very secret passphrase" 1.691 +# eap=TTLS PEAP TLS 1.692 +# identity="user@example.com" 1.693 +# password="foobar" 1.694 +# ca_cert="/etc/cert/ca.pem" 1.695 +# client_cert="/etc/cert/user.pem" 1.696 +# private_key="/etc/cert/user.prv" 1.697 +# private_key_passwd="password" 1.698 +# phase1="peaplabel=0" 1.699 +#} 1.700 + 1.701 +# Example of EAP-TLS with smartcard (openssl engine) 1.702 +#network={ 1.703 +# ssid="example" 1.704 +# key_mgmt=WPA-EAP 1.705 +# eap=TLS 1.706 +# proto=RSN 1.707 +# pairwise=CCMP TKIP 1.708 +# group=CCMP TKIP 1.709 +# identity="user@example.com" 1.710 +# ca_cert="/etc/cert/ca.pem" 1.711 +# client_cert="/etc/cert/user.pem" 1.712 +# 1.713 +# engine=1 1.714 + 1.715 + # The engine configured here must be available. Look at 1.716 + # OpenSSL engine support in the global section. 1.717 + # The key available through the engine must be the private key 1.718 + # matching the client certificate configured above. 1.719 + 1.720 + # use the opensc engine 1.721 + #engine_id="opensc" 1.722 + #key_id="45" 1.723 + 1.724 + # use the pkcs11 engine 1.725 +# engine_id="pkcs11" 1.726 +# key_id="id_45" 1.727 +# 1.728 + # Optional PIN configuration; this can be left out and PIN will be 1.729 + # asked through the control interface 1.730 +# pin="1234" 1.731 +#} 1.732 + 1.733 +# Example configuration showing how to use an inlined blob as a CA certificate 1.734 +# data instead of using external file 1.735 +#network={ 1.736 +# ssid="example" 1.737 +# key_mgmt=WPA-EAP 1.738 +# eap=TTLS 1.739 +# identity="user@example.com" 1.740 +# anonymous_identity="anonymous@example.com" 1.741 +# password="foobar" 1.742 +# ca_cert="blob://exampleblob" 1.743 +# priority=20 1.744 +#} 1.745 + 1.746 +#blob-base64-exampleblob={ 1.747 +#SGVsbG8gV29ybGQhCg== 1.748 +#} 1.749 + 1.750 + 1.751 +# Wildcard match for SSID (plaintext APs only). This example select any 1.752 +# open AP regardless of its SSID. 1.753 +network={ 1.754 + key_mgmt=NONE 1.755 +} 1.756 + 1.757 +