SliTaz Repositories

     1.1 --- a/wpa_supplicant/receipt	Sun Jun 14 14:30:11 2009 +0200
     1.2 +++ b/wpa_supplicant/receipt	Sun Jun 14 10:39:50 2009 +0000
     1.3 @@ -26,11 +26,15 @@
     1.4  	mkdir -p $fs/etc
     1.5  	cp -a $src/$PACKAGE/wpa_cli $fs/usr/bin
     1.6  	cp -a $src/$PACKAGE/wpa_supplicant $fs/usr/bin
     1.7 -	cp -a $src/$PACKAGE/wpa_passphrase $fs/usr/bin
     1.8 -	cp -a $src/$PACKAGE/wpa_supplicant.conf $fs/etc
     1.9 +	cp -a $src/$PACKAGE/wpa_passphrase $fs/usr/bin	
    1.10  	
    1.11 -	# Startup script
    1.12 +	# dont copy the original
    1.13 +	# cp -a $src/$PACKAGE/wpa_supplicant.conf $fs/etc
    1.14 +	
    1.15 +	# Startup script and cleaned up wpa_supplicant.conf
    1.16  	cp -a stuff/etc $fs
    1.17 +	
    1.18 +	
    1.19  }
    1.20  
    1.21  # Pre and post install commands for Tazpkg.

     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/wpa_supplicant/stuff/etc/wpa_supplicant.conf	Sun Jun 14 10:39:50 2009 +0000
     2.3 @@ -0,0 +1,754 @@
     2.4 +##### Example wpa_supplicant configuration file ###############################
     2.5 +#
     2.6 +# This file describes configuration file format and lists all available option.
     2.7 +# Please also take a look at simpler configuration examples in 'examples'
     2.8 +# subdirectory.
     2.9 +#
    2.10 +# Empty lines and lines starting with # are ignored
    2.11 +
    2.12 +# NOTE! This file may contain password information and should probably be made
    2.13 +# readable only by root user on multiuser systems.
    2.14 +
    2.15 +# Note: All file paths in this configuration file should use full (absolute,
    2.16 +# not relative to working directory) path in order to allow working directory
    2.17 +# to be changed. This can happen if wpa_supplicant is run in the background.
    2.18 +
    2.19 +# Whether to allow wpa_supplicant to update (overwrite) configuration
    2.20 +#
    2.21 +# This option can be used to allow wpa_supplicant to overwrite configuration
    2.22 +# file whenever configuration is changed (e.g., new network block is added with
    2.23 +# wpa_cli or wpa_gui, or a password is changed). This is required for
    2.24 +# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
    2.25 +# Please note that overwriting configuration file will remove the comments from
    2.26 +# it.
    2.27 +#update_config=1
    2.28 +
    2.29 +# global configuration (shared by all network blocks)
    2.30 +#
    2.31 +# Parameters for the control interface. If this is specified, wpa_supplicant
    2.32 +# will open a control interface that is available for external programs to
    2.33 +# manage wpa_supplicant. The meaning of this string depends on which control
    2.34 +# interface mechanism is used. For all cases, the existance of this parameter
    2.35 +# in configuration is used to determine whether the control interface is
    2.36 +# enabled.
    2.37 +#
    2.38 +# For UNIX domain sockets (default on Linux and BSD): This is a directory that
    2.39 +# will be created for UNIX domain sockets for listening to requests from
    2.40 +# external programs (CLI/GUI, etc.) for status information and configuration.
    2.41 +# The socket file will be named based on the interface name, so multiple
    2.42 +# wpa_supplicant processes can be run at the same time if more than one
    2.43 +# interface is used.
    2.44 +# /var/run/wpa_supplicant is the recommended directory for sockets and by
    2.45 +# default, wpa_cli will use it when trying to connect with wpa_supplicant.
    2.46 +#
    2.47 +# Access control for the control interface can be configured by setting the
    2.48 +# directory to allow only members of a group to use sockets. This way, it is
    2.49 +# possible to run wpa_supplicant as root (since it needs to change network
    2.50 +# configuration and open raw sockets) and still allow GUI/CLI components to be
    2.51 +# run as non-root users. However, since the control interface can be used to
    2.52 +# change the network configuration, this access needs to be protected in many
    2.53 +# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
    2.54 +# want to allow non-root users to use the control interface, add a new group
    2.55 +# and change this value to match with that group. Add users that should have
    2.56 +# control interface access to this group. If this variable is commented out or
    2.57 +# not included in the configuration file, group will not be changed from the
    2.58 +# value it got by default when the directory or socket was created.
    2.59 +#
    2.60 +# When configuring both the directory and group, use following format:
    2.61 +# DIR=/var/run/wpa_supplicant GROUP=wheel
    2.62 +# DIR=/var/run/wpa_supplicant GROUP=0
    2.63 +# (group can be either group name or gid)
    2.64 +#
    2.65 +# For UDP connections (default on Windows): The value will be ignored. This
    2.66 +# variable is just used to select that the control interface is to be created.
    2.67 +# The value can be set to, e.g., udp (ctrl_interface=udp)
    2.68 +#
    2.69 +# For Windows Named Pipe: This value can be used to set the security descriptor
    2.70 +# for controlling access to the control interface. Security descriptor can be
    2.71 +# set using Security Descriptor String Format (see http://msdn.microsoft.com/
    2.72 +# library/default.asp?url=/library/en-us/secauthz/security/
    2.73 +# security_descriptor_string_format.asp). The descriptor string needs to be
    2.74 +# prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty
    2.75 +# DACL (which will reject all connections). See README-Windows.txt for more
    2.76 +# information about SDDL string format.
    2.77 +#
    2.78 +ctrl_interface=/var/run/wpa_supplicant
    2.79 +
    2.80 +# Ensure that only root can read the WPA configuration
    2.81 +ctrl_interface_group=0
    2.82 +
    2.83 +
    2.84 +# IEEE 802.1X/EAPOL version
    2.85 +# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
    2.86 +# EAPOL version 2. However, there are many APs that do not handle the new
    2.87 +# version number correctly (they seem to drop the frames completely). In order
    2.88 +# to make wpa_supplicant interoperate with these APs, the version number is set
    2.89 +# to 1 by default. This configuration value can be used to set it to the new
    2.90 +# version (2).
    2.91 +eapol_version=1
    2.92 +
    2.93 +# AP scanning/selection
    2.94 +# By default, wpa_supplicant requests driver to perform AP scanning and then
    2.95 +# uses the scan results to select a suitable AP. Another alternative is to
    2.96 +# allow the driver to take care of AP scanning and selection and use
    2.97 +# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
    2.98 +# information from the driver.
    2.99 +# 1: wpa_supplicant initiates scanning and AP selection
   2.100 +# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
   2.101 +#    parameters (e.g., WPA IE generation); this mode can also be used with
   2.102 +#    non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
   2.103 +#    APs (i.e., external program needs to control association). This mode must
   2.104 +#    also be used when using wired Ethernet drivers.
   2.105 +# 2: like 0, but associate with APs using security policy and SSID (but not
   2.106 +#    BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
   2.107 +#    enable operation with hidden SSIDs and optimized roaming; in this mode,
   2.108 +#    the network blocks in the configuration file are tried one by one until
   2.109 +#    the driver reports successful association; each network block should have
   2.110 +#    explicit security policy (i.e., only one option in the lists) for
   2.111 +#    key_mgmt, pairwise, group, proto variables
   2.112 +ap_scan=1
   2.113 +
   2.114 +# EAP fast re-authentication
   2.115 +# By default, fast re-authentication is enabled for all EAP methods that
   2.116 +# support it. This variable can be used to disable fast re-authentication.
   2.117 +# Normally, there is no need to disable this.
   2.118 +fast_reauth=1
   2.119 +
   2.120 +# OpenSSL Engine support
   2.121 +# These options can be used to load OpenSSL engines.
   2.122 +# The two engines that are supported currently are shown below:
   2.123 +# They are both from the opensc project (http://www.opensc.org/)
   2.124 +# By default no engines are loaded.
   2.125 +# make the opensc engine available
   2.126 +#opensc_engine_path=/usr/lib/opensc/engine_opensc.so
   2.127 +# make the pkcs11 engine available
   2.128 +#pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
   2.129 +# configure the path to the pkcs11 module required by the pkcs11 engine
   2.130 +#pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
   2.131 +
   2.132 +# Dynamic EAP methods
   2.133 +# If EAP methods were built dynamically as shared object files, they need to be
   2.134 +# loaded here before being used in the network blocks. By default, EAP methods
   2.135 +# are included statically in the build, so these lines are not needed
   2.136 +#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
   2.137 +#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
   2.138 +
   2.139 +# Driver interface parameters
   2.140 +# This field can be used to configure arbitrary driver interace parameters. The
   2.141 +# format is specific to the selected driver interface. This field is not used
   2.142 +# in most cases.
   2.143 +#driver_param="field=value"
   2.144 +
   2.145 +# Maximum lifetime for PMKSA in seconds; default 43200
   2.146 +#dot11RSNAConfigPMKLifetime=43200
   2.147 +# Threshold for reauthentication (percentage of PMK lifetime); default 70
   2.148 +#dot11RSNAConfigPMKReauthThreshold=70
   2.149 +# Timeout for security association negotiation in seconds; default 60
   2.150 +#dot11RSNAConfigSATimeout=60
   2.151 +
   2.152 +# network block
   2.153 +#
   2.154 +# Each network (usually AP's sharing the same SSID) is configured as a separate
   2.155 +# block in this configuration file. The network blocks are in preference order
   2.156 +# (the first match is used).
   2.157 +#
   2.158 +# network block fields:
   2.159 +#
   2.160 +# disabled:
   2.161 +#	0 = this network can be used (default)
   2.162 +#	1 = this network block is disabled (can be enabled through ctrl_iface,
   2.163 +#	    e.g., with wpa_cli or wpa_gui)
   2.164 +#
   2.165 +# id_str: Network identifier string for external scripts. This value is passed
   2.166 +#	to external action script through wpa_cli as WPA_ID_STR environment
   2.167 +#	variable to make it easier to do network specific configuration.
   2.168 +#
   2.169 +# ssid: SSID (mandatory); either as an ASCII string with double quotation or
   2.170 +#	as hex string; network name
   2.171 +#
   2.172 +# scan_ssid:
   2.173 +#	0 = do not scan this SSID with specific Probe Request frames (default)
   2.174 +#	1 = scan with SSID-specific Probe Request frames (this can be used to
   2.175 +#	    find APs that do not accept broadcast SSID or use multiple SSIDs;
   2.176 +#	    this will add latency to scanning, so enable this only when needed)
   2.177 +#
   2.178 +# bssid: BSSID (optional); if set, this network block is used only when
   2.179 +#	associating with the AP using the configured BSSID
   2.180 +#
   2.181 +# priority: priority group (integer)
   2.182 +# By default, all networks will get same priority group (0). If some of the
   2.183 +# networks are more desirable, this field can be used to change the order in
   2.184 +# which wpa_supplicant goes through the networks when selecting a BSS. The
   2.185 +# priority groups will be iterated in decreasing priority (i.e., the larger the
   2.186 +# priority value, the sooner the network is matched against the scan results).
   2.187 +# Within each priority group, networks will be selected based on security
   2.188 +# policy, signal strength, etc.
   2.189 +# Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
   2.190 +# using this priority to select the order for scanning. Instead, they try the
   2.191 +# networks in the order that used in the configuration file.
   2.192 +#
   2.193 +# mode: IEEE 802.11 operation mode
   2.194 +# 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
   2.195 +# 1 = IBSS (ad-hoc, peer-to-peer)
   2.196 +# Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
   2.197 +# and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
   2.198 +# to be set to 2 for IBSS. WPA-None requires following network block options:
   2.199 +# proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
   2.200 +# both), and psk must also be set.
   2.201 +#
   2.202 +# frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
   2.203 +# 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
   2.204 +# channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
   2.205 +# In addition, this value is only used by the station that creates the IBSS. If
   2.206 +# an IBSS network with the configured SSID is already present, the frequency of
   2.207 +# the network will be used instead of this configured value.
   2.208 +#
   2.209 +# proto: list of accepted protocols
   2.210 +# WPA = WPA/IEEE 802.11i/D3.0
   2.211 +# RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
   2.212 +# If not set, this defaults to: WPA RSN
   2.213 +#
   2.214 +# key_mgmt: list of accepted authenticated key management protocols
   2.215 +# WPA-PSK = WPA pre-shared key (this requires 'psk' field)
   2.216 +# WPA-EAP = WPA using EAP authentication (this can use an external
   2.217 +#	program, e.g., Xsupplicant, for IEEE 802.1X EAP Authentication
   2.218 +# IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
   2.219 +#	generated WEP keys
   2.220 +# NONE = WPA is not used; plaintext or static WEP could be used
   2.221 +# If not set, this defaults to: WPA-PSK WPA-EAP
   2.222 +#
   2.223 +# auth_alg: list of allowed IEEE 802.11 authentication algorithms
   2.224 +# OPEN = Open System authentication (required for WPA/WPA2)
   2.225 +# SHARED = Shared Key authentication (requires static WEP keys)
   2.226 +# LEAP = LEAP/Network EAP (only used with LEAP)
   2.227 +# If not set, automatic selection is used (Open System with LEAP enabled if
   2.228 +# LEAP is allowed as one of the EAP methods).
   2.229 +#
   2.230 +# pairwise: list of accepted pairwise (unicast) ciphers for WPA
   2.231 +# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
   2.232 +# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
   2.233 +# NONE = Use only Group Keys (deprecated, should not be included if APs support
   2.234 +#	pairwise keys)
   2.235 +# If not set, this defaults to: CCMP TKIP
   2.236 +#
   2.237 +# group: list of accepted group (broadcast/multicast) ciphers for WPA
   2.238 +# CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
   2.239 +# TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
   2.240 +# WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
   2.241 +# WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
   2.242 +# If not set, this defaults to: CCMP TKIP WEP104 WEP40
   2.243 +#
   2.244 +# psk: WPA preshared key; 256-bit pre-shared key
   2.245 +# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
   2.246 +# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
   2.247 +# generated using the passphrase and SSID). ASCII passphrase must be between
   2.248 +# 8 and 63 characters (inclusive).
   2.249 +# This field is not needed, if WPA-EAP is used.
   2.250 +# Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
   2.251 +# from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
   2.252 +# startup and reconfiguration time can be optimized by generating the PSK only
   2.253 +# only when the passphrase or SSID has actually changed.
   2.254 +#
   2.255 +# eapol_flags: IEEE 802.1X/EAPOL options (bit field)
   2.256 +# Dynamic WEP key required for non-WPA mode
   2.257 +# bit0 (1): require dynamically generated unicast WEP key
   2.258 +# bit1 (2): require dynamically generated broadcast WEP key
   2.259 +# 	(3 = require both keys; default)
   2.260 +# Note: When using wired authentication, eapol_flags must be set to 0 for the
   2.261 +# authentication to be completed successfully.
   2.262 +#
   2.263 +# mixed_cell: This option can be used to configure whether so called mixed
   2.264 +# cells, i.e., networks that use both plaintext and encryption in the same
   2.265 +# SSID, are allowed when selecting a BSS form scan results.
   2.266 +# 0 = disabled (default)
   2.267 +# 1 = enabled
   2.268 +#
   2.269 +# proactive_key_caching:
   2.270 +# Enable/disable opportunistic PMKSA caching for WPA2.
   2.271 +# 0 = disabled (default)
   2.272 +# 1 = enabled
   2.273 +#
   2.274 +# wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
   2.275 +# hex without quotation, e.g., 0102030405)
   2.276 +# wep_tx_keyidx: Default WEP key index (TX) (0..3)
   2.277 +#
   2.278 +# peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
   2.279 +# allowed. This is only used with RSN/WPA2.
   2.280 +# 0 = disabled (default)
   2.281 +# 1 = enabled
   2.282 +#peerkey=1
   2.283 +#
   2.284 +# Following fields are only used with internal EAP implementation.
   2.285 +# eap: space-separated list of accepted EAP methods
   2.286 +#	MD5 = EAP-MD5 (unsecure and does not generate keying material ->
   2.287 +#			cannot be used with WPA; to be used as a Phase 2 method
   2.288 +#			with EAP-PEAP or EAP-TTLS)
   2.289 +#       MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
   2.290 +#		as a Phase 2 method with EAP-PEAP or EAP-TTLS)
   2.291 +#       OTP = EAP-OTP (cannot be used separately with WPA; to be used
   2.292 +#		as a Phase 2 method with EAP-PEAP or EAP-TTLS)
   2.293 +#       GTC = EAP-GTC (cannot be used separately with WPA; to be used
   2.294 +#		as a Phase 2 method with EAP-PEAP or EAP-TTLS)
   2.295 +#	TLS = EAP-TLS (client and server certificate)
   2.296 +#	PEAP = EAP-PEAP (with tunnelled EAP authentication)
   2.297 +#	TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
   2.298 +#			 authentication)
   2.299 +#	If not set, all compiled in methods are allowed.
   2.300 +#
   2.301 +# identity: Identity string for EAP
   2.302 +# anonymous_identity: Anonymous identity string for EAP (to be used as the
   2.303 +#	unencrypted identity with EAP types that support different tunnelled
   2.304 +#	identity, e.g., EAP-TTLS)
   2.305 +# password: Password string for EAP
   2.306 +# ca_cert: File path to CA certificate file (PEM/DER). This file can have one
   2.307 +#	or more trusted CA certificates. If ca_cert and ca_path are not
   2.308 +#	included, server certificate will not be verified. This is insecure and
   2.309 +#	a trusted CA certificate should always be configured when using
   2.310 +#	EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
   2.311 +#	change when wpa_supplicant is run in the background.
   2.312 +#	On Windows, trusted CA certificates can be loaded from the system
   2.313 +#	certificate store by setting this to cert_store://<name>, e.g.,
   2.314 +#	ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
   2.315 +#	Note that when running wpa_supplicant as an application, the user
   2.316 +#	certificate store (My user account) is used, whereas computer store
   2.317 +#	(Computer account) is used when running wpasvc as a service.
   2.318 +# ca_path: Directory path for CA certificate files (PEM). This path may
   2.319 +#	contain multiple CA certificates in OpenSSL format. Common use for this
   2.320 +#	is to point to system trusted CA list which is often installed into
   2.321 +#	directory like /etc/ssl/certs. If configured, these certificates are
   2.322 +#	added to the list of trusted CAs. ca_cert may also be included in that
   2.323 +#	case, but it is not required.
   2.324 +# client_cert: File path to client certificate file (PEM/DER)
   2.325 +#	Full path should be used since working directory may change when
   2.326 +#	wpa_supplicant is run in the background.
   2.327 +#	Alternatively, a named configuration blob can be used by setting this
   2.328 +#	to blob://<blob name>.
   2.329 +# private_key: File path to client private key file (PEM/DER/PFX)
   2.330 +#	When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
   2.331 +#	commented out. Both the private key and certificate will be read from
   2.332 +#	the PKCS#12 file in this case. Full path should be used since working
   2.333 +#	directory may change when wpa_supplicant is run in the background.
   2.334 +#	Windows certificate store can be used by leaving client_cert out and
   2.335 +#	configuring private_key in one of the following formats:
   2.336 +#	cert://substring_to_match
   2.337 +#	hash://certificate_thumbprint_in_hex
   2.338 +#	for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
   2.339 +#	Note that when running wpa_supplicant as an application, the user
   2.340 +#	certificate store (My user account) is used, whereas computer store
   2.341 +#	(Computer account) is used when running wpasvc as a service.
   2.342 +#	Alternatively, a named configuration blob can be used by setting this
   2.343 +#	to blob://<blob name>.
   2.344 +# private_key_passwd: Password for private key file (if left out, this will be
   2.345 +#	asked through control interface)
   2.346 +# dh_file: File path to DH/DSA parameters file (in PEM format)
   2.347 +#	This is an optional configuration file for setting parameters for an
   2.348 +#	ephemeral DH key exchange. In most cases, the default RSA
   2.349 +#	authentication does not use this configuration. However, it is possible
   2.350 +#	setup RSA to use ephemeral DH key exchange. In addition, ciphers with
   2.351 +#	DSA keys always use ephemeral DH keys. This can be used to achieve
   2.352 +#	forward secrecy. If the file is in DSA parameters format, it will be
   2.353 +#	automatically converted into DH params.
   2.354 +# subject_match: Substring to be matched against the subject of the
   2.355 +#	authentication server certificate. If this string is set, the server
   2.356 +#	sertificate is only accepted if it contains this string in the subject.
   2.357 +#	The subject string is in following format:
   2.358 +#	/C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
   2.359 +# altsubject_match: Semicolon separated string of entries to be matched against
   2.360 +#	the alternative subject name of the authentication server certificate.
   2.361 +#	If this string is set, the server sertificate is only accepted if it
   2.362 +#	contains one of the entries in an alternative subject name extension.
   2.363 +#	altSubjectName string is in following format: TYPE:VALUE
   2.364 +#	Example: EMAIL:server@example.com
   2.365 +#	Example: DNS:server.example.com;DNS:server2.example.com
   2.366 +#	Following types are supported: EMAIL, DNS, URI
   2.367 +# phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
   2.368 +#	(string with field-value pairs, e.g., "peapver=0" or
   2.369 +#	"peapver=1 peaplabel=1")
   2.370 +#	'peapver' can be used to force which PEAP version (0 or 1) is used.
   2.371 +#	'peaplabel=1' can be used to force new label, "client PEAP encryption",
   2.372 +#	to be used during key derivation when PEAPv1 or newer. Most existing
   2.373 +#	PEAPv1 implementation seem to be using the old label, "client EAP
   2.374 +#	encryption", and wpa_supplicant is now using that as the default value.
   2.375 +#	Some servers, e.g., Radiator, may require peaplabel=1 configuration to
   2.376 +#	interoperate with PEAPv1; see eap_testing.txt for more details.
   2.377 +#	'peap_outer_success=0' can be used to terminate PEAP authentication on
   2.378 +#	tunneled EAP-Success. This is required with some RADIUS servers that
   2.379 +#	implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
   2.380 +#	Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
   2.381 +#	include_tls_length=1 can be used to force wpa_supplicant to include
   2.382 +#	TLS Message Length field in all TLS messages even if they are not
   2.383 +#	fragmented.
   2.384 +#	sim_min_num_chal=3 can be used to configure EAP-SIM to require three
   2.385 +#	challenges (by default, it accepts 2 or 3)
   2.386 +# phase2: Phase2 (inner authentication with TLS tunnel) parameters
   2.387 +#	(string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
   2.388 +#	"autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
   2.389 +# Following certificate/private key fields are used in inner Phase2
   2.390 +# authentication when using EAP-TTLS or EAP-PEAP.
   2.391 +# ca_cert2: File path to CA certificate file. This file can have one or more
   2.392 +#	trusted CA certificates. If ca_cert2 and ca_path2 are not included,
   2.393 +#	server certificate will not be verified. This is insecure and a trusted
   2.394 +#	CA certificate should always be configured.
   2.395 +# ca_path2: Directory path for CA certificate files (PEM)
   2.396 +# client_cert2: File path to client certificate file
   2.397 +# private_key2: File path to client private key file
   2.398 +# private_key2_passwd: Password for private key file
   2.399 +# dh_file2: File path to DH/DSA parameters file (in PEM format)
   2.400 +# subject_match2: Substring to be matched against the subject of the
   2.401 +#	authentication server certificate.
   2.402 +# altsubject_match2: Substring to be matched against the alternative subject
   2.403 +#	name of the authentication server certificate.
   2.404 +#
   2.405 +# fragment_size: Maximum EAP fragment size in bytes (default 1398).
   2.406 +#	This value limits the fragment size for EAP methods that support
   2.407 +#	fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
   2.408 +#	small enough to make the EAP messages fit in MTU of the network
   2.409 +#	interface used for EAPOL. The default value is suitable for most
   2.410 +#	cases.
   2.411 +#
   2.412 +# EAP-PSK variables:
   2.413 +# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format
   2.414 +# nai: user NAI
   2.415 +#
   2.416 +# EAP-PAX variables:
   2.417 +# eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format
   2.418 +#
   2.419 +# EAP-SAKE variables:
   2.420 +# eappsk: 32-byte (256-bit, 64 hex digits) pre-shared key in hex format
   2.421 +#	(this is concatenation of Root-Secret-A and Root-Secret-B)
   2.422 +# nai: user NAI (PEERID)
   2.423 +#
   2.424 +# EAP-GPSK variables:
   2.425 +# eappsk: Pre-shared key in hex format (at least 128 bits, i.e., 32 hex digits)
   2.426 +# nai: user NAI (ID_Client)
   2.427 +#
   2.428 +# EAP-FAST variables:
   2.429 +# pac_file: File path for the PAC entries. wpa_supplicant will need to be able
   2.430 +#	to create this file and write updates to it when PAC is being
   2.431 +#	provisioned or refreshed. Full path to the file should be used since
   2.432 +#	working directory may change when wpa_supplicant is run in the
   2.433 +#	background. Alternatively, a named configuration blob can be used by
   2.434 +#	setting this to blob://<blob name>
   2.435 +# phase1: fast_provisioning=1 option enables in-line provisioning of EAP-FAST
   2.436 +#	credentials (PAC)
   2.437 +#
   2.438 +# wpa_supplicant supports number of "EAP workarounds" to work around
   2.439 +# interoperability issues with incorrectly behaving authentication servers.
   2.440 +# These are enabled by default because some of the issues are present in large
   2.441 +# number of authentication servers. Strict EAP conformance mode can be
   2.442 +# configured by disabling workarounds with eap_workaround=0.
   2.443 +
   2.444 +# Example blocks:
   2.445 +
   2.446 +# Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
   2.447 +#network={
   2.448 +#	ssid="simple"
   2.449 +#	psk="very secret passphrase"
   2.450 +#	priority=5
   2.451 +#}
   2.452 +
   2.453 +# Same as previous, but request SSID-specific scanning (for APs that reject
   2.454 +# broadcast SSID)
   2.455 +#network={
   2.456 +#	ssid="second ssid"
   2.457 +#	scan_ssid=1
   2.458 +#	psk="very secret passphrase"
   2.459 +#	priority=2
   2.460 +#}
   2.461 +
   2.462 +# Only WPA-PSK is used. Any valid cipher combination is accepted.
   2.463 +#network={
   2.464 +#	ssid="example"
   2.465 +#	proto=WPA
   2.466 +#	key_mgmt=WPA-PSK
   2.467 +#	pairwise=CCMP TKIP
   2.468 +#	group=CCMP TKIP WEP104 WEP40
   2.469 +#	psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
   2.470 +#	priority=2
   2.471 +#}
   2.472 +
   2.473 +# Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
   2.474 +# or WEP40 as the group cipher will not be accepted.
   2.475 +#network={
   2.476 +#	ssid="example"
   2.477 +#	proto=RSN
   2.478 +#	key_mgmt=WPA-EAP
   2.479 +#	pairwise=CCMP TKIP
   2.480 +#	group=CCMP TKIP
   2.481 +#	eap=TLS
   2.482 +#	identity="user@example.com"
   2.483 +#	ca_cert="/etc/cert/ca.pem"
   2.484 +#	client_cert="/etc/cert/user.pem"
   2.485 +#	private_key="/etc/cert/user.prv"
   2.486 +#	private_key_passwd="password"
   2.487 +#	priority=1
   2.488 +#}
   2.489 +
   2.490 +# EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
   2.491 +# (e.g., Radiator)
   2.492 +#network={
   2.493 +#	ssid="example"
   2.494 +#	key_mgmt=WPA-EAP
   2.495 +#	eap=PEAP
   2.496 +#	identity="user@example.com"
   2.497 +#	password="foobar"
   2.498 +#	ca_cert="/etc/cert/ca.pem"
   2.499 +#	phase1="peaplabel=1"
   2.500 +#	phase2="auth=MSCHAPV2"
   2.501 +#	priority=10
   2.502 +#}
   2.503 +
   2.504 +# EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
   2.505 +# unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
   2.506 +#network={
   2.507 +#	ssid="example"
   2.508 +#	key_mgmt=WPA-EAP
   2.509 +#	eap=TTLS
   2.510 +#	identity="user@example.com"
   2.511 +#	anonymous_identity="anonymous@example.com"
   2.512 +#	password="foobar"
   2.513 +#	ca_cert="/etc/cert/ca.pem"
   2.514 +#	priority=2
   2.515 +#}
   2.516 +
   2.517 +# EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
   2.518 +# use. Real identity is sent only within an encrypted TLS tunnel.
   2.519 +#network={
   2.520 +#	ssid="example"
   2.521 +#	key_mgmt=WPA-EAP
   2.522 +#	eap=TTLS
   2.523 +#	identity="user@example.com"
   2.524 +#	anonymous_identity="anonymous@example.com"
   2.525 +#	password="foobar"
   2.526 +#	ca_cert="/etc/cert/ca.pem"
   2.527 +#	phase2="auth=MSCHAPV2"
   2.528 +#}
   2.529 +
   2.530 +# WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
   2.531 +# authentication.
   2.532 +#network={
   2.533 +#	ssid="example"
   2.534 +#	key_mgmt=WPA-EAP
   2.535 +#	eap=TTLS
   2.536 +	# Phase1 / outer authentication
   2.537 +#	anonymous_identity="anonymous@example.com"
   2.538 +#	ca_cert="/etc/cert/ca.pem"
   2.539 +	# Phase 2 / inner authentication
   2.540 +#	phase2="autheap=TLS"
   2.541 +#	ca_cert2="/etc/cert/ca2.pem"
   2.542 +#	client_cert2="/etc/cer/user.pem"
   2.543 +#	private_key2="/etc/cer/user.prv"
   2.544 +#	private_key2_passwd="password"
   2.545 +#	priority=2
   2.546 +#}
   2.547 +
   2.548 +# Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
   2.549 +# group cipher.
   2.550 +#network={
   2.551 +#	ssid="example"
   2.552 +#	bssid=00:11:22:33:44:55
   2.553 +#	proto=WPA RSN
   2.554 +#	key_mgmt=WPA-PSK WPA-EAP
   2.555 +#	pairwise=CCMP
   2.556 +#	group=CCMP
   2.557 +#	psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
   2.558 +#}
   2.559 +
   2.560 +# Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
   2.561 +# and all valid ciphers.
   2.562 +#network={
   2.563 +#	ssid=00010203
   2.564 +#	psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
   2.565 +#}
   2.566 +
   2.567 +
   2.568 +# EAP-SIM with a GSM SIM or USIM
   2.569 +#network={
   2.570 +#	ssid="eap-sim-test"
   2.571 +#	key_mgmt=WPA-EAP
   2.572 +#	eap=SIM
   2.573 +#	pin="1234"
   2.574 +#	pcsc=""
   2.575 +#}
   2.576 +
   2.577 +
   2.578 +# EAP-PSK
   2.579 +#network={
   2.580 +#	ssid="eap-psk-test"
   2.581 +#	key_mgmt=WPA-EAP
   2.582 +#	eap=PSK
   2.583 +#	identity="eap_psk_user"
   2.584 +#	eappsk=06b4be19da289f475aa46a33cb793029
   2.585 +#	nai="eap_psk_user@example.com"
   2.586 +#}
   2.587 +
   2.588 +
   2.589 +# IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
   2.590 +# EAP-TLS for authentication and key generation; require both unicast and
   2.591 +# broadcast WEP keys.
   2.592 +#network={
   2.593 +#	ssid="1x-test"
   2.594 +#	key_mgmt=IEEE8021X
   2.595 +#	eap=TLS
   2.596 +#	identity="user@example.com"
   2.597 +#	ca_cert="/etc/cert/ca.pem"
   2.598 +#	client_cert="/etc/cert/user.pem"
   2.599 +#	private_key="/etc/cert/user.prv"
   2.600 +#	private_key_passwd="password"
   2.601 +#	eapol_flags=3
   2.602 +#}
   2.603 +
   2.604 +
   2.605 +# LEAP with dynamic WEP keys
   2.606 +#network={
   2.607 +#	ssid="leap-example"
   2.608 +#	key_mgmt=IEEE8021X
   2.609 +#	eap=LEAP
   2.610 +#	identity="user"
   2.611 +#	password="foobar"
   2.612 +#}
   2.613 +
   2.614 +# EAP-FAST with WPA (WPA or WPA2)
   2.615 +#network={
   2.616 +#	ssid="eap-fast-test"
   2.617 +#	key_mgmt=WPA-EAP
   2.618 +#	eap=FAST
   2.619 +#	anonymous_identity="FAST-000102030405"
   2.620 +#	identity="username"
   2.621 +#	password="password"
   2.622 +#	phase1="fast_provisioning=1"
   2.623 +#	pac_file="/etc/wpa_supplicant.eap-fast-pac"
   2.624 +#}
   2.625 +
   2.626 +#network={
   2.627 +#	ssid="eap-fast-test"
   2.628 +#	key_mgmt=WPA-EAP
   2.629 +#	eap=FAST
   2.630 +#	anonymous_identity="FAST-000102030405"
   2.631 +#	identity="username"
   2.632 +#	password="password"
   2.633 +#	phase1="fast_provisioning=1"
   2.634 +#	pac_file="blob://eap-fast-pac"
   2.635 +#}
   2.636 +
   2.637 +# Plaintext connection (no WPA, no IEEE 802.1X)
   2.638 +#network={
   2.639 +#	ssid="plaintext-test"
   2.640 +#	key_mgmt=NONE
   2.641 +#}
   2.642 +
   2.643 +
   2.644 +# Shared WEP key connection (no WPA, no IEEE 802.1X)
   2.645 +#network={
   2.646 +#	ssid="static-wep-test"
   2.647 +#	key_mgmt=NONE
   2.648 +#	wep_key0="abcde"
   2.649 +#	wep_key1=0102030405
   2.650 +#	wep_key2="1234567890123"
   2.651 +#	wep_tx_keyidx=0
   2.652 +#	priority=5
   2.653 +#}
   2.654 +
   2.655 +
   2.656 +# Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
   2.657 +# IEEE 802.11 authentication
   2.658 +#network={
   2.659 +#	ssid="static-wep-test2"
   2.660 +#	key_mgmt=NONE
   2.661 +#	wep_key0="abcde"
   2.662 +#	wep_key1=0102030405
   2.663 +#	wep_key2="1234567890123"
   2.664 +#	wep_tx_keyidx=0
   2.665 +#	priority=5
   2.666 +#	auth_alg=SHARED
   2.667 +#}
   2.668 +
   2.669 +
   2.670 +# IBSS/ad-hoc network with WPA-None/TKIP.
   2.671 +#network={
   2.672 +#	ssid="test adhoc"
   2.673 +#	mode=1
   2.674 +#	frequency=2412
   2.675 +#	proto=WPA
   2.676 +#	key_mgmt=WPA-NONE
   2.677 +#	pairwise=NONE
   2.678 +#	group=TKIP
   2.679 +#	psk="secret passphrase"
   2.680 +#}
   2.681 +
   2.682 +
   2.683 +# Catch all example that allows more or less all configuration modes
   2.684 +#network={
   2.685 +#	ssid="example"
   2.686 +#	scan_ssid=1
   2.687 +#	key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
   2.688 +#	pairwise=CCMP TKIP
   2.689 +#	group=CCMP TKIP WEP104 WEP40
   2.690 +#	psk="very secret passphrase"
   2.691 +#	eap=TTLS PEAP TLS
   2.692 +#	identity="user@example.com"
   2.693 +#	password="foobar"
   2.694 +#	ca_cert="/etc/cert/ca.pem"
   2.695 +#	client_cert="/etc/cert/user.pem"
   2.696 +#	private_key="/etc/cert/user.prv"
   2.697 +#	private_key_passwd="password"
   2.698 +#	phase1="peaplabel=0"
   2.699 +#}
   2.700 +
   2.701 +# Example of EAP-TLS with smartcard (openssl engine)
   2.702 +#network={
   2.703 +#	ssid="example"
   2.704 +#	key_mgmt=WPA-EAP
   2.705 +#	eap=TLS
   2.706 +#	proto=RSN
   2.707 +#	pairwise=CCMP TKIP
   2.708 +#	group=CCMP TKIP
   2.709 +#	identity="user@example.com"
   2.710 +#	ca_cert="/etc/cert/ca.pem"
   2.711 +#	client_cert="/etc/cert/user.pem"
   2.712 +#
   2.713 +#	engine=1
   2.714 +
   2.715 +	# The engine configured here must be available. Look at
   2.716 +	# OpenSSL engine support in the global section.
   2.717 +	# The key available through the engine must be the private key
   2.718 +	# matching the client certificate configured above.
   2.719 +
   2.720 +	# use the opensc engine
   2.721 +	#engine_id="opensc"
   2.722 +	#key_id="45"
   2.723 +
   2.724 +	# use the pkcs11 engine
   2.725 +#	engine_id="pkcs11"
   2.726 +#	key_id="id_45"
   2.727 +#
   2.728 +	# Optional PIN configuration; this can be left out and PIN will be
   2.729 +	# asked through the control interface
   2.730 +#	pin="1234"
   2.731 +#}
   2.732 +
   2.733 +# Example configuration showing how to use an inlined blob as a CA certificate
   2.734 +# data instead of using external file
   2.735 +#network={
   2.736 +#	ssid="example"
   2.737 +#	key_mgmt=WPA-EAP
   2.738 +#	eap=TTLS
   2.739 +#	identity="user@example.com"
   2.740 +#	anonymous_identity="anonymous@example.com"
   2.741 +#	password="foobar"
   2.742 +#	ca_cert="blob://exampleblob"
   2.743 +#	priority=20
   2.744 +#}
   2.745 +
   2.746 +#blob-base64-exampleblob={
   2.747 +#SGVsbG8gV29ybGQhCg==
   2.748 +#}
   2.749 +
   2.750 +
   2.751 +# Wildcard match for SSID (plaintext APs only). This example select any
   2.752 +# open AP regardless of its SSID.
   2.753 +network={
   2.754 +	key_mgmt=NONE
   2.755 +}
   2.756 +
   2.757 +