wok-6.x view wpa_supplicant/stuff/etc/wpa_supplicant.conf @ rev 13443
Add: claws-mail-attachwarner
| author | Eric Joseph-Alexandre <erjo@slitaz.org> |
|---|---|
| date | Sun Oct 07 01:24:00 2012 +0200 (2012-10-07) |
| parents | |
| children | 01ad1e61b761 |
line source
1 ##### Example wpa_supplicant configuration file ###############################
2 #
3 # This file describes configuration file format and lists all available option.
4 # Please also take a look at simpler configuration examples in 'examples'
5 # subdirectory.
6 #
7 # Empty lines and lines starting with # are ignored
9 # NOTE! This file may contain password information and should probably be made
10 # readable only by root user on multiuser systems.
12 # Note: All file paths in this configuration file should use full (absolute,
13 # not relative to working directory) path in order to allow working directory
14 # to be changed. This can happen if wpa_supplicant is run in the background.
16 # Whether to allow wpa_supplicant to update (overwrite) configuration
17 #
18 # This option can be used to allow wpa_supplicant to overwrite configuration
19 # file whenever configuration is changed (e.g., new network block is added with
20 # wpa_cli or wpa_gui, or a password is changed). This is required for
21 # wpa_cli/wpa_gui to be able to store the configuration changes permanently.
22 # Please note that overwriting configuration file will remove the comments from
23 # it.
24 #update_config=1
26 # global configuration (shared by all network blocks)
27 #
28 # Parameters for the control interface. If this is specified, wpa_supplicant
29 # will open a control interface that is available for external programs to
30 # manage wpa_supplicant. The meaning of this string depends on which control
31 # interface mechanism is used. For all cases, the existance of this parameter
32 # in configuration is used to determine whether the control interface is
33 # enabled.
34 #
35 # For UNIX domain sockets (default on Linux and BSD): This is a directory that
36 # will be created for UNIX domain sockets for listening to requests from
37 # external programs (CLI/GUI, etc.) for status information and configuration.
38 # The socket file will be named based on the interface name, so multiple
39 # wpa_supplicant processes can be run at the same time if more than one
40 # interface is used.
41 # /var/run/wpa_supplicant is the recommended directory for sockets and by
42 # default, wpa_cli will use it when trying to connect with wpa_supplicant.
43 #
44 # Access control for the control interface can be configured by setting the
45 # directory to allow only members of a group to use sockets. This way, it is
46 # possible to run wpa_supplicant as root (since it needs to change network
47 # configuration and open raw sockets) and still allow GUI/CLI components to be
48 # run as non-root users. However, since the control interface can be used to
49 # change the network configuration, this access needs to be protected in many
50 # cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
51 # want to allow non-root users to use the control interface, add a new group
52 # and change this value to match with that group. Add users that should have
53 # control interface access to this group. If this variable is commented out or
54 # not included in the configuration file, group will not be changed from the
55 # value it got by default when the directory or socket was created.
56 #
57 # When configuring both the directory and group, use following format:
58 # DIR=/var/run/wpa_supplicant GROUP=wheel
59 # DIR=/var/run/wpa_supplicant GROUP=0
60 # (group can be either group name or gid)
61 #
62 # For UDP connections (default on Windows): The value will be ignored. This
63 # variable is just used to select that the control interface is to be created.
64 # The value can be set to, e.g., udp (ctrl_interface=udp)
65 #
66 # For Windows Named Pipe: This value can be used to set the security descriptor
67 # for controlling access to the control interface. Security descriptor can be
68 # set using Security Descriptor String Format (see http://msdn.microsoft.com/
69 # library/default.asp?url=/library/en-us/secauthz/security/
70 # security_descriptor_string_format.asp). The descriptor string needs to be
71 # prefixed with SDDL=. For example, ctrl_interface=SDDL=D: would set an empty
72 # DACL (which will reject all connections). See README-Windows.txt for more
73 # information about SDDL string format.
74 #
75 ctrl_interface=/var/run/wpa_supplicant
77 # Ensure that only root can read the WPA configuration
78 ctrl_interface_group=0
81 # IEEE 802.1X/EAPOL version
82 # wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
83 # EAPOL version 2. However, there are many APs that do not handle the new
84 # version number correctly (they seem to drop the frames completely). In order
85 # to make wpa_supplicant interoperate with these APs, the version number is set
86 # to 1 by default. This configuration value can be used to set it to the new
87 # version (2).
88 eapol_version=1
90 # AP scanning/selection
91 # By default, wpa_supplicant requests driver to perform AP scanning and then
92 # uses the scan results to select a suitable AP. Another alternative is to
93 # allow the driver to take care of AP scanning and selection and use
94 # wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
95 # information from the driver.
96 # 1: wpa_supplicant initiates scanning and AP selection
97 # 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
98 # parameters (e.g., WPA IE generation); this mode can also be used with
99 # non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
100 # APs (i.e., external program needs to control association). This mode must
101 # also be used when using wired Ethernet drivers.
102 # 2: like 0, but associate with APs using security policy and SSID (but not
103 # BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
104 # enable operation with hidden SSIDs and optimized roaming; in this mode,
105 # the network blocks in the configuration file are tried one by one until
106 # the driver reports successful association; each network block should have
107 # explicit security policy (i.e., only one option in the lists) for
108 # key_mgmt, pairwise, group, proto variables
109 ap_scan=1
111 # EAP fast re-authentication
112 # By default, fast re-authentication is enabled for all EAP methods that
113 # support it. This variable can be used to disable fast re-authentication.
114 # Normally, there is no need to disable this.
115 fast_reauth=1
117 # OpenSSL Engine support
118 # These options can be used to load OpenSSL engines.
119 # The two engines that are supported currently are shown below:
120 # They are both from the opensc project (http://www.opensc.org/)
121 # By default no engines are loaded.
122 # make the opensc engine available
123 #opensc_engine_path=/usr/lib/opensc/engine_opensc.so
124 # make the pkcs11 engine available
125 #pkcs11_engine_path=/usr/lib/opensc/engine_pkcs11.so
126 # configure the path to the pkcs11 module required by the pkcs11 engine
127 #pkcs11_module_path=/usr/lib/pkcs11/opensc-pkcs11.so
129 # Dynamic EAP methods
130 # If EAP methods were built dynamically as shared object files, they need to be
131 # loaded here before being used in the network blocks. By default, EAP methods
132 # are included statically in the build, so these lines are not needed
133 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_tls.so
134 #load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
136 # Driver interface parameters
137 # This field can be used to configure arbitrary driver interace parameters. The
138 # format is specific to the selected driver interface. This field is not used
139 # in most cases.
140 #driver_param="field=value"
142 # Maximum lifetime for PMKSA in seconds; default 43200
143 #dot11RSNAConfigPMKLifetime=43200
144 # Threshold for reauthentication (percentage of PMK lifetime); default 70
145 #dot11RSNAConfigPMKReauthThreshold=70
146 # Timeout for security association negotiation in seconds; default 60
147 #dot11RSNAConfigSATimeout=60
149 # network block
150 #
151 # Each network (usually AP's sharing the same SSID) is configured as a separate
152 # block in this configuration file. The network blocks are in preference order
153 # (the first match is used).
154 #
155 # network block fields:
156 #
157 # disabled:
158 # 0 = this network can be used (default)
159 # 1 = this network block is disabled (can be enabled through ctrl_iface,
160 # e.g., with wpa_cli or wpa_gui)
161 #
162 # id_str: Network identifier string for external scripts. This value is passed
163 # to external action script through wpa_cli as WPA_ID_STR environment
164 # variable to make it easier to do network specific configuration.
165 #
166 # ssid: SSID (mandatory); either as an ASCII string with double quotation or
167 # as hex string; network name
168 #
169 # scan_ssid:
170 # 0 = do not scan this SSID with specific Probe Request frames (default)
171 # 1 = scan with SSID-specific Probe Request frames (this can be used to
172 # find APs that do not accept broadcast SSID or use multiple SSIDs;
173 # this will add latency to scanning, so enable this only when needed)
174 #
175 # bssid: BSSID (optional); if set, this network block is used only when
176 # associating with the AP using the configured BSSID
177 #
178 # priority: priority group (integer)
179 # By default, all networks will get same priority group (0). If some of the
180 # networks are more desirable, this field can be used to change the order in
181 # which wpa_supplicant goes through the networks when selecting a BSS. The
182 # priority groups will be iterated in decreasing priority (i.e., the larger the
183 # priority value, the sooner the network is matched against the scan results).
184 # Within each priority group, networks will be selected based on security
185 # policy, signal strength, etc.
186 # Please note that AP scanning with scan_ssid=1 and ap_scan=2 mode are not
187 # using this priority to select the order for scanning. Instead, they try the
188 # networks in the order that used in the configuration file.
189 #
190 # mode: IEEE 802.11 operation mode
191 # 0 = infrastructure (Managed) mode, i.e., associate with an AP (default)
192 # 1 = IBSS (ad-hoc, peer-to-peer)
193 # Note: IBSS can only be used with key_mgmt NONE (plaintext and static WEP)
194 # and key_mgmt=WPA-NONE (fixed group key TKIP/CCMP). In addition, ap_scan has
195 # to be set to 2 for IBSS. WPA-None requires following network block options:
196 # proto=WPA, key_mgmt=WPA-NONE, pairwise=NONE, group=TKIP (or CCMP, but not
197 # both), and psk must also be set.
198 #
199 # frequency: Channel frequency in megahertz (MHz) for IBSS, e.g.,
200 # 2412 = IEEE 802.11b/g channel 1. This value is used to configure the initial
201 # channel for IBSS (adhoc) networks. It is ignored in the infrastructure mode.
202 # In addition, this value is only used by the station that creates the IBSS. If
203 # an IBSS network with the configured SSID is already present, the frequency of
204 # the network will be used instead of this configured value.
205 #
206 # proto: list of accepted protocols
207 # WPA = WPA/IEEE 802.11i/D3.0
208 # RSN = WPA2/IEEE 802.11i (also WPA2 can be used as an alias for RSN)
209 # If not set, this defaults to: WPA RSN
210 #
211 # key_mgmt: list of accepted authenticated key management protocols
212 # WPA-PSK = WPA pre-shared key (this requires 'psk' field)
213 # WPA-EAP = WPA using EAP authentication (this can use an external
214 # program, e.g., Xsupplicant, for IEEE 802.1X EAP Authentication
215 # IEEE8021X = IEEE 802.1X using EAP authentication and (optionally) dynamically
216 # generated WEP keys
217 # NONE = WPA is not used; plaintext or static WEP could be used
218 # If not set, this defaults to: WPA-PSK WPA-EAP
219 #
220 # auth_alg: list of allowed IEEE 802.11 authentication algorithms
221 # OPEN = Open System authentication (required for WPA/WPA2)
222 # SHARED = Shared Key authentication (requires static WEP keys)
223 # LEAP = LEAP/Network EAP (only used with LEAP)
224 # If not set, automatic selection is used (Open System with LEAP enabled if
225 # LEAP is allowed as one of the EAP methods).
226 #
227 # pairwise: list of accepted pairwise (unicast) ciphers for WPA
228 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
229 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
230 # NONE = Use only Group Keys (deprecated, should not be included if APs support
231 # pairwise keys)
232 # If not set, this defaults to: CCMP TKIP
233 #
234 # group: list of accepted group (broadcast/multicast) ciphers for WPA
235 # CCMP = AES in Counter mode with CBC-MAC [RFC 3610, IEEE 802.11i/D7.0]
236 # TKIP = Temporal Key Integrity Protocol [IEEE 802.11i/D7.0]
237 # WEP104 = WEP (Wired Equivalent Privacy) with 104-bit key
238 # WEP40 = WEP (Wired Equivalent Privacy) with 40-bit key [IEEE 802.11]
239 # If not set, this defaults to: CCMP TKIP WEP104 WEP40
240 #
241 # psk: WPA preshared key; 256-bit pre-shared key
242 # The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
243 # 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
244 # generated using the passphrase and SSID). ASCII passphrase must be between
245 # 8 and 63 characters (inclusive).
246 # This field is not needed, if WPA-EAP is used.
247 # Note: Separate tool, wpa_passphrase, can be used to generate 256-bit keys
248 # from ASCII passphrase. This process uses lot of CPU and wpa_supplicant
249 # startup and reconfiguration time can be optimized by generating the PSK only
250 # only when the passphrase or SSID has actually changed.
251 #
252 # eapol_flags: IEEE 802.1X/EAPOL options (bit field)
253 # Dynamic WEP key required for non-WPA mode
254 # bit0 (1): require dynamically generated unicast WEP key
255 # bit1 (2): require dynamically generated broadcast WEP key
256 # (3 = require both keys; default)
257 # Note: When using wired authentication, eapol_flags must be set to 0 for the
258 # authentication to be completed successfully.
259 #
260 # mixed_cell: This option can be used to configure whether so called mixed
261 # cells, i.e., networks that use both plaintext and encryption in the same
262 # SSID, are allowed when selecting a BSS form scan results.
263 # 0 = disabled (default)
264 # 1 = enabled
265 #
266 # proactive_key_caching:
267 # Enable/disable opportunistic PMKSA caching for WPA2.
268 # 0 = disabled (default)
269 # 1 = enabled
270 #
271 # wep_key0..3: Static WEP key (ASCII in double quotation, e.g. "abcde" or
272 # hex without quotation, e.g., 0102030405)
273 # wep_tx_keyidx: Default WEP key index (TX) (0..3)
274 #
275 # peerkey: Whether PeerKey negotiation for direct links (IEEE 802.11e DLS) is
276 # allowed. This is only used with RSN/WPA2.
277 # 0 = disabled (default)
278 # 1 = enabled
279 #peerkey=1
280 #
281 # Following fields are only used with internal EAP implementation.
282 # eap: space-separated list of accepted EAP methods
283 # MD5 = EAP-MD5 (unsecure and does not generate keying material ->
284 # cannot be used with WPA; to be used as a Phase 2 method
285 # with EAP-PEAP or EAP-TTLS)
286 # MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
287 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
288 # OTP = EAP-OTP (cannot be used separately with WPA; to be used
289 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
290 # GTC = EAP-GTC (cannot be used separately with WPA; to be used
291 # as a Phase 2 method with EAP-PEAP or EAP-TTLS)
292 # TLS = EAP-TLS (client and server certificate)
293 # PEAP = EAP-PEAP (with tunnelled EAP authentication)
294 # TTLS = EAP-TTLS (with tunnelled EAP or PAP/CHAP/MSCHAP/MSCHAPV2
295 # authentication)
296 # If not set, all compiled in methods are allowed.
297 #
298 # identity: Identity string for EAP
299 # anonymous_identity: Anonymous identity string for EAP (to be used as the
300 # unencrypted identity with EAP types that support different tunnelled
301 # identity, e.g., EAP-TTLS)
302 # password: Password string for EAP
303 # ca_cert: File path to CA certificate file (PEM/DER). This file can have one
304 # or more trusted CA certificates. If ca_cert and ca_path are not
305 # included, server certificate will not be verified. This is insecure and
306 # a trusted CA certificate should always be configured when using
307 # EAP-TLS/TTLS/PEAP. Full path should be used since working directory may
308 # change when wpa_supplicant is run in the background.
309 # On Windows, trusted CA certificates can be loaded from the system
310 # certificate store by setting this to cert_store://<name>, e.g.,
311 # ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
312 # Note that when running wpa_supplicant as an application, the user
313 # certificate store (My user account) is used, whereas computer store
314 # (Computer account) is used when running wpasvc as a service.
315 # ca_path: Directory path for CA certificate files (PEM). This path may
316 # contain multiple CA certificates in OpenSSL format. Common use for this
317 # is to point to system trusted CA list which is often installed into
318 # directory like /etc/ssl/certs. If configured, these certificates are
319 # added to the list of trusted CAs. ca_cert may also be included in that
320 # case, but it is not required.
321 # client_cert: File path to client certificate file (PEM/DER)
322 # Full path should be used since working directory may change when
323 # wpa_supplicant is run in the background.
324 # Alternatively, a named configuration blob can be used by setting this
325 # to blob://<blob name>.
326 # private_key: File path to client private key file (PEM/DER/PFX)
327 # When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
328 # commented out. Both the private key and certificate will be read from
329 # the PKCS#12 file in this case. Full path should be used since working
330 # directory may change when wpa_supplicant is run in the background.
331 # Windows certificate store can be used by leaving client_cert out and
332 # configuring private_key in one of the following formats:
333 # cert://substring_to_match
334 # hash://certificate_thumbprint_in_hex
335 # for example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
336 # Note that when running wpa_supplicant as an application, the user
337 # certificate store (My user account) is used, whereas computer store
338 # (Computer account) is used when running wpasvc as a service.
339 # Alternatively, a named configuration blob can be used by setting this
340 # to blob://<blob name>.
341 # private_key_passwd: Password for private key file (if left out, this will be
342 # asked through control interface)
343 # dh_file: File path to DH/DSA parameters file (in PEM format)
344 # This is an optional configuration file for setting parameters for an
345 # ephemeral DH key exchange. In most cases, the default RSA
346 # authentication does not use this configuration. However, it is possible
347 # setup RSA to use ephemeral DH key exchange. In addition, ciphers with
348 # DSA keys always use ephemeral DH keys. This can be used to achieve
349 # forward secrecy. If the file is in DSA parameters format, it will be
350 # automatically converted into DH params.
351 # subject_match: Substring to be matched against the subject of the
352 # authentication server certificate. If this string is set, the server
353 # sertificate is only accepted if it contains this string in the subject.
354 # The subject string is in following format:
355 # /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
356 # altsubject_match: Semicolon separated string of entries to be matched against
357 # the alternative subject name of the authentication server certificate.
358 # If this string is set, the server sertificate is only accepted if it
359 # contains one of the entries in an alternative subject name extension.
360 # altSubjectName string is in following format: TYPE:VALUE
361 # Example: EMAIL:server@example.com
362 # Example: DNS:server.example.com;DNS:server2.example.com
363 # Following types are supported: EMAIL, DNS, URI
364 # phase1: Phase1 (outer authentication, i.e., TLS tunnel) parameters
365 # (string with field-value pairs, e.g., "peapver=0" or
366 # "peapver=1 peaplabel=1")
367 # 'peapver' can be used to force which PEAP version (0 or 1) is used.
368 # 'peaplabel=1' can be used to force new label, "client PEAP encryption",
369 # to be used during key derivation when PEAPv1 or newer. Most existing
370 # PEAPv1 implementation seem to be using the old label, "client EAP
371 # encryption", and wpa_supplicant is now using that as the default value.
372 # Some servers, e.g., Radiator, may require peaplabel=1 configuration to
373 # interoperate with PEAPv1; see eap_testing.txt for more details.
374 # 'peap_outer_success=0' can be used to terminate PEAP authentication on
375 # tunneled EAP-Success. This is required with some RADIUS servers that
376 # implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
377 # Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode)
378 # include_tls_length=1 can be used to force wpa_supplicant to include
379 # TLS Message Length field in all TLS messages even if they are not
380 # fragmented.
381 # sim_min_num_chal=3 can be used to configure EAP-SIM to require three
382 # challenges (by default, it accepts 2 or 3)
383 # phase2: Phase2 (inner authentication with TLS tunnel) parameters
384 # (string with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
385 # "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS)
386 # Following certificate/private key fields are used in inner Phase2
387 # authentication when using EAP-TTLS or EAP-PEAP.
388 # ca_cert2: File path to CA certificate file. This file can have one or more
389 # trusted CA certificates. If ca_cert2 and ca_path2 are not included,
390 # server certificate will not be verified. This is insecure and a trusted
391 # CA certificate should always be configured.
392 # ca_path2: Directory path for CA certificate files (PEM)
393 # client_cert2: File path to client certificate file
394 # private_key2: File path to client private key file
395 # private_key2_passwd: Password for private key file
396 # dh_file2: File path to DH/DSA parameters file (in PEM format)
397 # subject_match2: Substring to be matched against the subject of the
398 # authentication server certificate.
399 # altsubject_match2: Substring to be matched against the alternative subject
400 # name of the authentication server certificate.
401 #
402 # fragment_size: Maximum EAP fragment size in bytes (default 1398).
403 # This value limits the fragment size for EAP methods that support
404 # fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
405 # small enough to make the EAP messages fit in MTU of the network
406 # interface used for EAPOL. The default value is suitable for most
407 # cases.
408 #
409 # EAP-PSK variables:
410 # eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format
411 # nai: user NAI
412 #
413 # EAP-PAX variables:
414 # eappsk: 16-byte (128-bit, 32 hex digits) pre-shared key in hex format
415 #
416 # EAP-SAKE variables:
417 # eappsk: 32-byte (256-bit, 64 hex digits) pre-shared key in hex format
418 # (this is concatenation of Root-Secret-A and Root-Secret-B)
419 # nai: user NAI (PEERID)
420 #
421 # EAP-GPSK variables:
422 # eappsk: Pre-shared key in hex format (at least 128 bits, i.e., 32 hex digits)
423 # nai: user NAI (ID_Client)
424 #
425 # EAP-FAST variables:
426 # pac_file: File path for the PAC entries. wpa_supplicant will need to be able
427 # to create this file and write updates to it when PAC is being
428 # provisioned or refreshed. Full path to the file should be used since
429 # working directory may change when wpa_supplicant is run in the
430 # background. Alternatively, a named configuration blob can be used by
431 # setting this to blob://<blob name>
432 # phase1: fast_provisioning=1 option enables in-line provisioning of EAP-FAST
433 # credentials (PAC)
434 #
435 # wpa_supplicant supports number of "EAP workarounds" to work around
436 # interoperability issues with incorrectly behaving authentication servers.
437 # These are enabled by default because some of the issues are present in large
438 # number of authentication servers. Strict EAP conformance mode can be
439 # configured by disabling workarounds with eap_workaround=0.
441 # Example blocks:
443 # Simple case: WPA-PSK, PSK as an ASCII passphrase, allow all valid ciphers
444 #network={
445 # ssid="simple"
446 # psk="very secret passphrase"
447 # priority=5
448 #}
450 # Same as previous, but request SSID-specific scanning (for APs that reject
451 # broadcast SSID)
452 #network={
453 # ssid="second ssid"
454 # scan_ssid=1
455 # psk="very secret passphrase"
456 # priority=2
457 #}
459 # Only WPA-PSK is used. Any valid cipher combination is accepted.
460 #network={
461 # ssid="example"
462 # proto=WPA
463 # key_mgmt=WPA-PSK
464 # pairwise=CCMP TKIP
465 # group=CCMP TKIP WEP104 WEP40
466 # psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
467 # priority=2
468 #}
470 # Only WPA-EAP is used. Both CCMP and TKIP is accepted. An AP that used WEP104
471 # or WEP40 as the group cipher will not be accepted.
472 #network={
473 # ssid="example"
474 # proto=RSN
475 # key_mgmt=WPA-EAP
476 # pairwise=CCMP TKIP
477 # group=CCMP TKIP
478 # eap=TLS
479 # identity="user@example.com"
480 # ca_cert="/etc/cert/ca.pem"
481 # client_cert="/etc/cert/user.pem"
482 # private_key="/etc/cert/user.prv"
483 # private_key_passwd="password"
484 # priority=1
485 #}
487 # EAP-PEAP/MSCHAPv2 configuration for RADIUS servers that use the new peaplabel
488 # (e.g., Radiator)
489 #network={
490 # ssid="example"
491 # key_mgmt=WPA-EAP
492 # eap=PEAP
493 # identity="user@example.com"
494 # password="foobar"
495 # ca_cert="/etc/cert/ca.pem"
496 # phase1="peaplabel=1"
497 # phase2="auth=MSCHAPV2"
498 # priority=10
499 #}
501 # EAP-TTLS/EAP-MD5-Challenge configuration with anonymous identity for the
502 # unencrypted use. Real identity is sent only within an encrypted TLS tunnel.
503 #network={
504 # ssid="example"
505 # key_mgmt=WPA-EAP
506 # eap=TTLS
507 # identity="user@example.com"
508 # anonymous_identity="anonymous@example.com"
509 # password="foobar"
510 # ca_cert="/etc/cert/ca.pem"
511 # priority=2
512 #}
514 # EAP-TTLS/MSCHAPv2 configuration with anonymous identity for the unencrypted
515 # use. Real identity is sent only within an encrypted TLS tunnel.
516 #network={
517 # ssid="example"
518 # key_mgmt=WPA-EAP
519 # eap=TTLS
520 # identity="user@example.com"
521 # anonymous_identity="anonymous@example.com"
522 # password="foobar"
523 # ca_cert="/etc/cert/ca.pem"
524 # phase2="auth=MSCHAPV2"
525 #}
527 # WPA-EAP, EAP-TTLS with different CA certificate used for outer and inner
528 # authentication.
529 #network={
530 # ssid="example"
531 # key_mgmt=WPA-EAP
532 # eap=TTLS
533 # Phase1 / outer authentication
534 # anonymous_identity="anonymous@example.com"
535 # ca_cert="/etc/cert/ca.pem"
536 # Phase 2 / inner authentication
537 # phase2="autheap=TLS"
538 # ca_cert2="/etc/cert/ca2.pem"
539 # client_cert2="/etc/cer/user.pem"
540 # private_key2="/etc/cer/user.prv"
541 # private_key2_passwd="password"
542 # priority=2
543 #}
545 # Both WPA-PSK and WPA-EAP is accepted. Only CCMP is accepted as pairwise and
546 # group cipher.
547 #network={
548 # ssid="example"
549 # bssid=00:11:22:33:44:55
550 # proto=WPA RSN
551 # key_mgmt=WPA-PSK WPA-EAP
552 # pairwise=CCMP
553 # group=CCMP
554 # psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb
555 #}
557 # Special characters in SSID, so use hex string. Default to WPA-PSK, WPA-EAP
558 # and all valid ciphers.
559 #network={
560 # ssid=00010203
561 # psk=000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
562 #}
565 # EAP-SIM with a GSM SIM or USIM
566 #network={
567 # ssid="eap-sim-test"
568 # key_mgmt=WPA-EAP
569 # eap=SIM
570 # pin="1234"
571 # pcsc=""
572 #}
575 # EAP-PSK
576 #network={
577 # ssid="eap-psk-test"
578 # key_mgmt=WPA-EAP
579 # eap=PSK
580 # identity="eap_psk_user"
581 # eappsk=06b4be19da289f475aa46a33cb793029
582 # nai="eap_psk_user@example.com"
583 #}
586 # IEEE 802.1X/EAPOL with dynamically generated WEP keys (i.e., no WPA) using
587 # EAP-TLS for authentication and key generation; require both unicast and
588 # broadcast WEP keys.
589 #network={
590 # ssid="1x-test"
591 # key_mgmt=IEEE8021X
592 # eap=TLS
593 # identity="user@example.com"
594 # ca_cert="/etc/cert/ca.pem"
595 # client_cert="/etc/cert/user.pem"
596 # private_key="/etc/cert/user.prv"
597 # private_key_passwd="password"
598 # eapol_flags=3
599 #}
602 # LEAP with dynamic WEP keys
603 #network={
604 # ssid="leap-example"
605 # key_mgmt=IEEE8021X
606 # eap=LEAP
607 # identity="user"
608 # password="foobar"
609 #}
611 # EAP-FAST with WPA (WPA or WPA2)
612 #network={
613 # ssid="eap-fast-test"
614 # key_mgmt=WPA-EAP
615 # eap=FAST
616 # anonymous_identity="FAST-000102030405"
617 # identity="username"
618 # password="password"
619 # phase1="fast_provisioning=1"
620 # pac_file="/etc/wpa_supplicant.eap-fast-pac"
621 #}
623 #network={
624 # ssid="eap-fast-test"
625 # key_mgmt=WPA-EAP
626 # eap=FAST
627 # anonymous_identity="FAST-000102030405"
628 # identity="username"
629 # password="password"
630 # phase1="fast_provisioning=1"
631 # pac_file="blob://eap-fast-pac"
632 #}
634 # Plaintext connection (no WPA, no IEEE 802.1X)
635 #network={
636 # ssid="plaintext-test"
637 # key_mgmt=NONE
638 #}
641 # Shared WEP key connection (no WPA, no IEEE 802.1X)
642 #network={
643 # ssid="static-wep-test"
644 # key_mgmt=NONE
645 # wep_key0="abcde"
646 # wep_key1=0102030405
647 # wep_key2="1234567890123"
648 # wep_tx_keyidx=0
649 # priority=5
650 #}
653 # Shared WEP key connection (no WPA, no IEEE 802.1X) using Shared Key
654 # IEEE 802.11 authentication
655 #network={
656 # ssid="static-wep-test2"
657 # key_mgmt=NONE
658 # wep_key0="abcde"
659 # wep_key1=0102030405
660 # wep_key2="1234567890123"
661 # wep_tx_keyidx=0
662 # priority=5
663 # auth_alg=SHARED
664 #}
667 # IBSS/ad-hoc network with WPA-None/TKIP.
668 #network={
669 # ssid="test adhoc"
670 # mode=1
671 # frequency=2412
672 # proto=WPA
673 # key_mgmt=WPA-NONE
674 # pairwise=NONE
675 # group=TKIP
676 # psk="secret passphrase"
677 #}
680 # Catch all example that allows more or less all configuration modes
681 #network={
682 # ssid="example"
683 # scan_ssid=1
684 # key_mgmt=WPA-EAP WPA-PSK IEEE8021X NONE
685 # pairwise=CCMP TKIP
686 # group=CCMP TKIP WEP104 WEP40
687 # psk="very secret passphrase"
688 # eap=TTLS PEAP TLS
689 # identity="user@example.com"
690 # password="foobar"
691 # ca_cert="/etc/cert/ca.pem"
692 # client_cert="/etc/cert/user.pem"
693 # private_key="/etc/cert/user.prv"
694 # private_key_passwd="password"
695 # phase1="peaplabel=0"
696 #}
698 # Example of EAP-TLS with smartcard (openssl engine)
699 #network={
700 # ssid="example"
701 # key_mgmt=WPA-EAP
702 # eap=TLS
703 # proto=RSN
704 # pairwise=CCMP TKIP
705 # group=CCMP TKIP
706 # identity="user@example.com"
707 # ca_cert="/etc/cert/ca.pem"
708 # client_cert="/etc/cert/user.pem"
709 #
710 # engine=1
712 # The engine configured here must be available. Look at
713 # OpenSSL engine support in the global section.
714 # The key available through the engine must be the private key
715 # matching the client certificate configured above.
717 # use the opensc engine
718 #engine_id="opensc"
719 #key_id="45"
721 # use the pkcs11 engine
722 # engine_id="pkcs11"
723 # key_id="id_45"
724 #
725 # Optional PIN configuration; this can be left out and PIN will be
726 # asked through the control interface
727 # pin="1234"
728 #}
730 # Example configuration showing how to use an inlined blob as a CA certificate
731 # data instead of using external file
732 #network={
733 # ssid="example"
734 # key_mgmt=WPA-EAP
735 # eap=TTLS
736 # identity="user@example.com"
737 # anonymous_identity="anonymous@example.com"
738 # password="foobar"
739 # ca_cert="blob://exampleblob"
740 # priority=20
741 #}
743 #blob-base64-exampleblob={
744 #SGVsbG8gV29ybGQhCg==
745 #}
748 # Wildcard match for SSID (plaintext APs only). This example select any
749 # open AP regardless of its SSID.
750 network={
751 key_mgmt=NONE
752 }