2 * EAP peer configuration data
3 * Copyright (c) 2003-2008, Jouni Malinen <j@w1.fi>
5 * This software may be distributed under the terms of the BSD license.
6 * See README for more details.
13 * struct eap_peer_config - EAP peer configuration/credentials
15 struct eap_peer_config {
17 * identity - EAP Identity
19 * This field is used to set the real user identity or NAI (for
20 * EAP-PSK/PAX/SAKE/GPSK).
25 * identity_len - EAP Identity length
30 * anonymous_identity - Anonymous EAP Identity
32 * This field is used for unencrypted use with EAP types that support
33 * different tunnelled identity, e.g., EAP-TTLS, in order to reveal the
34 * real identity (identity field) only to the authentication server.
36 * If not set, the identity field will be used for both unencrypted and
39 u8 *anonymous_identity;
42 * anonymous_identity_len - Length of anonymous_identity
44 size_t anonymous_identity_len;
47 * password - Password string for EAP
49 * This field can include either the plaintext password (default
50 * option) or a NtPasswordHash (16-byte MD4 hash of the unicode
51 * presentation of the password) if flags field has
52 * EAP_CONFIG_FLAGS_PASSWORD_NTHASH bit set to 1. NtPasswordHash can
53 * only be used with authentication mechanism that use this hash as the
54 * starting point for operation: MSCHAP and MSCHAPv2 (EAP-MSCHAPv2,
55 * EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP).
57 * In addition, this field is used to configure a pre-shared key for
58 * EAP-PSK/PAX/SAKE/GPSK. The length of the PSK must be 16 for EAP-PSK
59 * and EAP-PAX and 32 for EAP-SAKE. EAP-GPSK can use a variable length
65 * password_len - Length of password field
70 * ca_cert - File path to CA certificate file (PEM/DER)
72 * This file can have one or more trusted CA certificates. If ca_cert
73 * and ca_path are not included, server certificate will not be
74 * verified. This is insecure and a trusted CA certificate should
75 * always be configured when using EAP-TLS/TTLS/PEAP. Full path to the
76 * file should be used since working directory may change when
77 * wpa_supplicant is run in the background.
79 * Alternatively, a named configuration blob can be used by setting
80 * this to blob://blob_name.
82 * Alternatively, this can be used to only perform matching of the
83 * server certificate (SHA-256 hash of the DER encoded X.509
84 * certificate). In this case, the possible CA certificates in the
85 * server certificate chain are ignored and only the server certificate
86 * is verified. This is configured with the following format:
87 * hash:://server/sha256/cert_hash_in_hex
88 * For example: "hash://server/sha256/
89 * 5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a"
91 * On Windows, trusted CA certificates can be loaded from the system
92 * certificate store by setting this to cert_store://name, e.g.,
93 * ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT".
94 * Note that when running wpa_supplicant as an application, the user
95 * certificate store (My user account) is used, whereas computer store
96 * (Computer account) is used when running wpasvc as a service.
101 * ca_path - Directory path for CA certificate files (PEM)
103 * This path may contain multiple CA certificates in OpenSSL format.
104 * Common use for this is to point to system trusted CA list which is
105 * often installed into directory like /etc/ssl/certs. If configured,
106 * these certificates are added to the list of trusted CAs. ca_cert
107 * may also be included in that case, but it is not required.
112 * client_cert - File path to client certificate file (PEM/DER)
114 * This field is used with EAP method that use TLS authentication.
115 * Usually, this is only configured for EAP-TLS, even though this could
116 * in theory be used with EAP-TTLS and EAP-PEAP, too. Full path to the
117 * file should be used since working directory may change when
118 * wpa_supplicant is run in the background.
120 * Alternatively, a named configuration blob can be used by setting
121 * this to blob://blob_name.
126 * private_key - File path to client private key file (PEM/DER/PFX)
128 * When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
129 * commented out. Both the private key and certificate will be read
130 * from the PKCS#12 file in this case. Full path to the file should be
131 * used since working directory may change when wpa_supplicant is run
134 * Windows certificate store can be used by leaving client_cert out and
135 * configuring private_key in one of the following formats:
137 * cert://substring_to_match
139 * hash://certificate_thumbprint_in_hex
141 * For example: private_key="hash://63093aa9c47f56ae88334c7b65a4"
143 * Note that when running wpa_supplicant as an application, the user
144 * certificate store (My user account) is used, whereas computer store
145 * (Computer account) is used when running wpasvc as a service.
147 * Alternatively, a named configuration blob can be used by setting
148 * this to blob://blob_name.
153 * private_key_passwd - Password for private key file
155 * If left out, this will be asked through control interface.
157 u8 *private_key_passwd;
160 * dh_file - File path to DH/DSA parameters file (in PEM format)
162 * This is an optional configuration file for setting parameters for an
163 * ephemeral DH key exchange. In most cases, the default RSA
164 * authentication does not use this configuration. However, it is
165 * possible setup RSA to use ephemeral DH key exchange. In addition,
166 * ciphers with DSA keys always use ephemeral DH keys. This can be used
167 * to achieve forward secrecy. If the file is in DSA parameters format,
168 * it will be automatically converted into DH params. Full path to the
169 * file should be used since working directory may change when
170 * wpa_supplicant is run in the background.
172 * Alternatively, a named configuration blob can be used by setting
173 * this to blob://blob_name.
178 * subject_match - Constraint for server certificate subject
180 * This substring is matched against the subject of the authentication
181 * server certificate. If this string is set, the server sertificate is
182 * only accepted if it contains this string in the subject. The subject
183 * string is in following format:
185 * /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@n.example.com
190 * altsubject_match - Constraint for server certificate alt. subject
192 * Semicolon separated string of entries to be matched against the
193 * alternative subject name of the authentication server certificate.
194 * If this string is set, the server sertificate is only accepted if it
195 * contains one of the entries in an alternative subject name
198 * altSubjectName string is in following format: TYPE:VALUE
200 * Example: EMAIL:server@example.com
201 * Example: DNS:server.example.com;DNS:server2.example.com
203 * Following types are supported: EMAIL, DNS, URI
205 u8 *altsubject_match;
208 * ca_cert2 - File path to CA certificate file (PEM/DER) (Phase 2)
210 * This file can have one or more trusted CA certificates. If ca_cert2
211 * and ca_path2 are not included, server certificate will not be
212 * verified. This is insecure and a trusted CA certificate should
213 * always be configured. Full path to the file should be used since
214 * working directory may change when wpa_supplicant is run in the
217 * This field is like ca_cert, but used for phase 2 (inside
218 * EAP-TTLS/PEAP/FAST tunnel) authentication.
220 * Alternatively, a named configuration blob can be used by setting
221 * this to blob://blob_name.
226 * ca_path2 - Directory path for CA certificate files (PEM) (Phase 2)
228 * This path may contain multiple CA certificates in OpenSSL format.
229 * Common use for this is to point to system trusted CA list which is
230 * often installed into directory like /etc/ssl/certs. If configured,
231 * these certificates are added to the list of trusted CAs. ca_cert
232 * may also be included in that case, but it is not required.
234 * This field is like ca_path, but used for phase 2 (inside
235 * EAP-TTLS/PEAP/FAST tunnel) authentication.
240 * client_cert2 - File path to client certificate file
242 * This field is like client_cert, but used for phase 2 (inside
243 * EAP-TTLS/PEAP/FAST tunnel) authentication. Full path to the
244 * file should be used since working directory may change when
245 * wpa_supplicant is run in the background.
247 * Alternatively, a named configuration blob can be used by setting
248 * this to blob://blob_name.
253 * private_key2 - File path to client private key file
255 * This field is like private_key, but used for phase 2 (inside
256 * EAP-TTLS/PEAP/FAST tunnel) authentication. Full path to the
257 * file should be used since working directory may change when
258 * wpa_supplicant is run in the background.
260 * Alternatively, a named configuration blob can be used by setting
261 * this to blob://blob_name.
266 * private_key2_passwd - Password for private key file
268 * This field is like private_key_passwd, but used for phase 2 (inside
269 * EAP-TTLS/PEAP/FAST tunnel) authentication.
271 u8 *private_key2_passwd;
274 * dh_file2 - File path to DH/DSA parameters file (in PEM format)
276 * This field is like dh_file, but used for phase 2 (inside
277 * EAP-TTLS/PEAP/FAST tunnel) authentication. Full path to the
278 * file should be used since working directory may change when
279 * wpa_supplicant is run in the background.
281 * Alternatively, a named configuration blob can be used by setting
282 * this to blob://blob_name.
287 * subject_match2 - Constraint for server certificate subject
289 * This field is like subject_match, but used for phase 2 (inside
290 * EAP-TTLS/PEAP/FAST tunnel) authentication.
295 * altsubject_match2 - Constraint for server certificate alt. subject
297 * This field is like altsubject_match, but used for phase 2 (inside
298 * EAP-TTLS/PEAP/FAST tunnel) authentication.
300 u8 *altsubject_match2;
303 * eap_methods - Allowed EAP methods
305 * (vendor=EAP_VENDOR_IETF,method=EAP_TYPE_NONE) terminated list of
306 * allowed EAP methods or %NULL if all methods are accepted.
308 struct eap_method_type *eap_methods;
311 * phase1 - Phase 1 (outer authentication) parameters
313 * String with field-value pairs, e.g., "peapver=0" or
314 * "peapver=1 peaplabel=1".
316 * 'peapver' can be used to force which PEAP version (0 or 1) is used.
318 * 'peaplabel=1' can be used to force new label, "client PEAP
319 * encryption", to be used during key derivation when PEAPv1 or newer.
321 * Most existing PEAPv1 implementation seem to be using the old label,
322 * "client EAP encryption", and wpa_supplicant is now using that as the
325 * Some servers, e.g., Radiator, may require peaplabel=1 configuration
326 * to interoperate with PEAPv1; see eap_testing.txt for more details.
328 * 'peap_outer_success=0' can be used to terminate PEAP authentication
329 * on tunneled EAP-Success. This is required with some RADIUS servers
330 * that implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g.,
331 * Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode).
333 * include_tls_length=1 can be used to force wpa_supplicant to include
334 * TLS Message Length field in all TLS messages even if they are not
337 * sim_min_num_chal=3 can be used to configure EAP-SIM to require three
338 * challenges (by default, it accepts 2 or 3).
340 * result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
341 * protected result indication.
343 * fast_provisioning option can be used to enable in-line provisioning
344 * of EAP-FAST credentials (PAC):
346 * 1 = allow unauthenticated provisioning,
347 * 2 = allow authenticated provisioning,
348 * 3 = allow both unauthenticated and authenticated provisioning
350 * fast_max_pac_list_len=num option can be used to set the maximum
351 * number of PAC entries to store in a PAC list (default: 10).
353 * fast_pac_format=binary option can be used to select binary format
354 * for storing PAC entries in order to save some space (the default
355 * text format uses about 2.5 times the size of minimal binary format).
357 * crypto_binding option can be used to control PEAPv0 cryptobinding
359 * 0 = do not use cryptobinding (default)
360 * 1 = use cryptobinding if server supports it
361 * 2 = require cryptobinding
363 * EAP-WSC (WPS) uses following options: pin=Device_Password and
369 * phase2 - Phase2 (inner authentication with TLS tunnel) parameters
371 * String with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or
372 * "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS.
377 * pcsc - Parameters for PC/SC smartcard interface for USIM and GSM SIM
379 * This field is used to configure PC/SC smartcard interface.
380 * Currently, the only configuration is whether this field is %NULL (do
381 * not use PC/SC) or non-NULL (e.g., "") to enable PC/SC.
383 * This field is used for EAP-SIM and EAP-AKA.
388 * pin - PIN for USIM, GSM SIM, and smartcards
390 * This field is used to configure PIN for SIM and smartcards for
391 * EAP-SIM and EAP-AKA. In addition, this is used with EAP-TLS if a
392 * smartcard is used for private key operations.
394 * If left out, this will be asked through control interface.
399 * engine - Enable OpenSSL engine (e.g., for smartcard access)
401 * This is used if private key operations for EAP-TLS are performed
407 * engine_id - Engine ID for OpenSSL engine
409 * "opensc" to select OpenSC engine or "pkcs11" to select PKCS#11
412 * This is used if private key operations for EAP-TLS are performed
418 * engine2 - Enable OpenSSL engine (e.g., for smartcard) (Phase 2)
420 * This is used if private key operations for EAP-TLS are performed
423 * This field is like engine, but used for phase 2 (inside
424 * EAP-TTLS/PEAP/FAST tunnel) authentication.
430 * pin2 - PIN for USIM, GSM SIM, and smartcards (Phase 2)
432 * This field is used to configure PIN for SIM and smartcards for
433 * EAP-SIM and EAP-AKA. In addition, this is used with EAP-TLS if a
434 * smartcard is used for private key operations.
436 * This field is like pin2, but used for phase 2 (inside
437 * EAP-TTLS/PEAP/FAST tunnel) authentication.
439 * If left out, this will be asked through control interface.
444 * engine2_id - Engine ID for OpenSSL engine (Phase 2)
446 * "opensc" to select OpenSC engine or "pkcs11" to select PKCS#11
449 * This is used if private key operations for EAP-TLS are performed
452 * This field is like engine_id, but used for phase 2 (inside
453 * EAP-TTLS/PEAP/FAST tunnel) authentication.
459 * key_id - Key ID for OpenSSL engine
461 * This is used if private key operations for EAP-TLS are performed
467 * cert_id - Cert ID for OpenSSL engine
469 * This is used if the certificate operations for EAP-TLS are performed
475 * ca_cert_id - CA Cert ID for OpenSSL engine
477 * This is used if the CA certificate for EAP-TLS is on a smartcard.
482 * key2_id - Key ID for OpenSSL engine (phase2)
484 * This is used if private key operations for EAP-TLS are performed
490 * cert2_id - Cert ID for OpenSSL engine (phase2)
492 * This is used if the certificate operations for EAP-TLS are performed
498 * ca_cert2_id - CA Cert ID for OpenSSL engine (phase2)
500 * This is used if the CA certificate for EAP-TLS is on a smartcard.
505 * otp - One-time-password
507 * This field should not be set in configuration step. It is only used
508 * internally when OTP is entered through the control interface.
513 * otp_len - Length of the otp field
518 * pending_req_identity - Whether there is a pending identity request
520 * This field should not be set in configuration step. It is only used
521 * internally when control interface is used to request needed
524 int pending_req_identity;
527 * pending_req_password - Whether there is a pending password request
529 * This field should not be set in configuration step. It is only used
530 * internally when control interface is used to request needed
533 int pending_req_password;
536 * pending_req_pin - Whether there is a pending PIN request
538 * This field should not be set in configuration step. It is only used
539 * internally when control interface is used to request needed
545 * pending_req_new_password - Pending password update request
547 * This field should not be set in configuration step. It is only used
548 * internally when control interface is used to request needed
551 int pending_req_new_password;
554 * pending_req_passphrase - Pending passphrase request
556 * This field should not be set in configuration step. It is only used
557 * internally when control interface is used to request needed
560 int pending_req_passphrase;
563 * pending_req_otp - Whether there is a pending OTP request
565 * This field should not be set in configuration step. It is only used
566 * internally when control interface is used to request needed
569 char *pending_req_otp;
572 * pending_req_otp_len - Length of the pending OTP request
574 size_t pending_req_otp_len;
577 * pac_file - File path or blob name for the PAC entries (EAP-FAST)
579 * wpa_supplicant will need to be able to create this file and write
580 * updates to it when PAC is being provisioned or refreshed. Full path
581 * to the file should be used since working directory may change when
582 * wpa_supplicant is run in the background.
583 * Alternatively, a named configuration blob can be used by setting
584 * this to blob://blob_name.
589 * mschapv2_retry - MSCHAPv2 retry in progress
591 * This field is used internally by EAP-MSCHAPv2 and should not be set
592 * as part of configuration.
597 * new_password - New password for password update
599 * This field is used during MSCHAPv2 password update. This is normally
600 * requested from the user through the control interface and not set
601 * from configuration.
606 * new_password_len - Length of new_password field
608 size_t new_password_len;
611 * fragment_size - Maximum EAP fragment size in bytes (default 1398)
613 * This value limits the fragment size for EAP methods that support
614 * fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set
615 * small enough to make the EAP messages fit in MTU of the network
616 * interface used for EAPOL. The default value is suitable for most
621 #define EAP_CONFIG_FLAGS_PASSWORD_NTHASH BIT(0)
623 * flags - Network configuration flags (bitfield)
625 * This variable is used for internal flags to describe further details
626 * for the network parameters.
627 * bit 0 = password is represented as a 16-byte NtPasswordHash value
628 * instead of plaintext password
635 * struct wpa_config_blob - Named configuration blob
637 * This data structure is used to provide storage for binary objects to store
638 * abstract information like certificates and private keys inlined with the
639 * configuration data.
641 struct wpa_config_blob {
648 * data - Pointer to binary data
653 * len - Length of binary data
658 * next - Pointer to next blob in the configuration
660 struct wpa_config_blob *next;
663 #endif /* EAP_CONFIG_H */