1 /* 2 * EAP peer configuration data 3 * Copyright (c) 2003-2019, Jouni Malinen <j@w1.fi> 4 * 5 * This software may be distributed under the terms of the BSD license. 6 * See README for more details. 7 */ 8 9 #ifndef EAP_CONFIG_H 10 #define EAP_CONFIG_H 11 12 /** 13 * struct eap_peer_cert_config - EAP peer certificate configuration/credential 14 */ 15 struct eap_peer_cert_config { 16 /** 17 * ca_cert - File path to CA certificate file (PEM/DER) 18 * 19 * This file can have one or more trusted CA certificates. If ca_cert 20 * and ca_path are not included, server certificate will not be 21 * verified. This is insecure and a trusted CA certificate should 22 * always be configured when using EAP-TLS/TTLS/PEAP. Full path to the 23 * file should be used since working directory may change when 24 * wpa_supplicant is run in the background. 25 * 26 * Alternatively, a named configuration blob can be used by setting 27 * this to blob://blob_name. 28 * 29 * Alternatively, this can be used to only perform matching of the 30 * server certificate (SHA-256 hash of the DER encoded X.509 31 * certificate). In this case, the possible CA certificates in the 32 * server certificate chain are ignored and only the server certificate 33 * is verified. This is configured with the following format: 34 * hash:://server/sha256/cert_hash_in_hex 35 * For example: "hash://server/sha256/ 36 * 5a1bc1296205e6fdbe3979728efe3920798885c1c4590b5f90f43222d239ca6a" 37 * 38 * On Windows, trusted CA certificates can be loaded from the system 39 * certificate store by setting this to cert_store://name, e.g., 40 * ca_cert="cert_store://CA" or ca_cert="cert_store://ROOT". 41 * Note that when running wpa_supplicant as an application, the user 42 * certificate store (My user account) is used, whereas computer store 43 * (Computer account) is used when running wpasvc as a service. 44 */ 45 char *ca_cert; 46 47 /** 48 * ca_path - Directory path for CA certificate files (PEM) 49 * 50 * This path may contain multiple CA certificates in OpenSSL format. 51 * Common use for this is to point to system trusted CA list which is 52 * often installed into directory like /etc/ssl/certs. If configured, 53 * these certificates are added to the list of trusted CAs. ca_cert 54 * may also be included in that case, but it is not required. 55 */ 56 char *ca_path; 57 58 /** 59 * client_cert - File path to client certificate file (PEM/DER) 60 * 61 * This field is used with EAP method that use TLS authentication. 62 * Usually, this is only configured for EAP-TLS, even though this could 63 * in theory be used with EAP-TTLS and EAP-PEAP, too. Full path to the 64 * file should be used since working directory may change when 65 * wpa_supplicant is run in the background. 66 * 67 * Alternatively, a named configuration blob can be used by setting 68 * this to blob://blob_name. 69 */ 70 char *client_cert; 71 72 /** 73 * private_key - File path to client private key file (PEM/DER/PFX) 74 * 75 * When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be 76 * commented out. Both the private key and certificate will be read 77 * from the PKCS#12 file in this case. Full path to the file should be 78 * used since working directory may change when wpa_supplicant is run 79 * in the background. 80 * 81 * Windows certificate store can be used by leaving client_cert out and 82 * configuring private_key in one of the following formats: 83 * 84 * cert://substring_to_match 85 * 86 * hash://certificate_thumbprint_in_hex 87 * 88 * For example: private_key="hash://63093aa9c47f56ae88334c7b65a4" 89 * 90 * Note that when running wpa_supplicant as an application, the user 91 * certificate store (My user account) is used, whereas computer store 92 * (Computer account) is used when running wpasvc as a service. 93 * 94 * Alternatively, a named configuration blob can be used by setting 95 * this to blob://blob_name. 96 */ 97 char *private_key; 98 99 /** 100 * private_key_passwd - Password for private key file 101 * 102 * If left out, this will be asked through control interface. 103 */ 104 char *private_key_passwd; 105 106 /** 107 * subject_match - Constraint for server certificate subject 108 * 109 * This substring is matched against the subject of the authentication 110 * server certificate. If this string is set, the server certificate is 111 * only accepted if it contains this string in the subject. The subject 112 * string is in following format: 113 * 114 * /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@n.example.com 115 * 116 * Note: Since this is a substring match, this cannot be used securely 117 * to do a suffix match against a possible domain name in the CN entry. 118 * For such a use case, domain_suffix_match should be used instead. 119 */ 120 char *subject_match; 121 122 /** 123 * check_cert_subject - Constraint for server certificate subject fields 124 * 125 * If check_cert_subject is set, the value of every field will be 126 * checked against the DN of the subject in the authentication server 127 * certificate. If the values do not match, the certificate verification 128 * will fail, rejecting the server. This option allows wpa_supplicant to 129 * match every individual field in the right order against the DN of the 130 * subject in the server certificate. 131 * 132 * For example, check_cert_subject=C=US/O=XX/OU=ABC/OU=XYZ/CN=1234 will 133 * check every individual DN field of the subject in the server 134 * certificate. If OU=XYZ comes first in terms of the order in the 135 * server certificate (DN field of server certificate 136 * C=US/O=XX/OU=XYZ/OU=ABC/CN=1234), wpa_supplicant will reject the 137 * server because the order of 'OU' is not matching the specified string 138 * in check_cert_subject. 139 * 140 * This option also allows '*' as a wildcard. This option has some 141 * limitation. 142 * It can only be used as per the following example. 143 * 144 * For example, check_cert_subject=C=US/O=XX/OU=Production* and we have 145 * two servers and DN of the subject in the first server certificate is 146 * (C=US/O=XX/OU=Production Unit) and DN of the subject in the second 147 * server is (C=US/O=XX/OU=Production Factory). In this case, 148 * wpa_supplicant will allow both servers because the value of 'OU' 149 * field in both server certificates matches 'OU' value in 150 * 'check_cert_subject' up to 'wildcard'. 151 * 152 * (Allow all servers, e.g., check_cert_subject=*) 153 */ 154 char *check_cert_subject; 155 156 /** 157 * altsubject_match - Constraint for server certificate alt. subject 158 * 159 * Semicolon separated string of entries to be matched against the 160 * alternative subject name of the authentication server certificate. 161 * If this string is set, the server certificate is only accepted if it 162 * contains one of the entries in an alternative subject name 163 * extension. 164 * 165 * altSubjectName string is in following format: TYPE:VALUE 166 * 167 * Example: EMAIL:server@example.com 168 * Example: DNS:server.example.com;DNS:server2.example.com 169 * 170 * Following types are supported: EMAIL, DNS, URI 171 */ 172 char *altsubject_match; 173 174 /** 175 * domain_suffix_match - Constraint for server domain name 176 * 177 * If set, this semicolon deliminated list of FQDNs is used as suffix 178 * match requirements for the server certificate in SubjectAltName 179 * dNSName element(s). If a matching dNSName is found against any of the 180 * specified values, this constraint is met. If no dNSName values are 181 * present, this constraint is matched against SubjectName CN using same 182 * suffix match comparison. Suffix match here means that the host/domain 183 * name is compared case-insentively one label at a time starting from 184 * the top-level domain and all the labels in domain_suffix_match shall 185 * be included in the certificate. The certificate may include 186 * additional sub-level labels in addition to the required labels. 187 * 188 * For example, domain_suffix_match=example.com would match 189 * test.example.com but would not match test-example.com. Multiple 190 * match options can be specified in following manner: 191 * example.org;example.com. 192 */ 193 char *domain_suffix_match; 194 195 /** 196 * domain_match - Constraint for server domain name 197 * 198 * If set, this FQDN is used as a full match requirement for the 199 * server certificate in SubjectAltName dNSName element(s). If a 200 * matching dNSName is found, this constraint is met. If no dNSName 201 * values are present, this constraint is matched against SubjectName CN 202 * using same full match comparison. This behavior is similar to 203 * domain_suffix_match, but has the requirement of a full match, i.e., 204 * no subdomains or wildcard matches are allowed. Case-insensitive 205 * comparison is used, so "Example.com" matches "example.com", but would 206 * not match "test.Example.com". 207 * 208 * More than one match string can be provided by using semicolons to 209 * separate the strings (e.g., example.org;example.com). When multiple 210 * strings are specified, a match with any one of the values is 211 * considered a sufficient match for the certificate, i.e., the 212 * conditions are ORed together. 213 */ 214 char *domain_match; 215 216 /** 217 * pin - PIN for USIM, GSM SIM, and smartcards 218 * 219 * This field is used to configure PIN for SIM and smartcards for 220 * EAP-SIM and EAP-AKA. In addition, this is used with EAP-TLS if a 221 * smartcard is used for private key operations. 222 * 223 * If left out, this will be asked through control interface. 224 */ 225 char *pin; 226 227 /** 228 * engine - Enable OpenSSL engine (e.g., for smartcard access) 229 * 230 * This is used if private key operations for EAP-TLS are performed 231 * using a smartcard. 232 */ 233 int engine; 234 235 /** 236 * engine_id - Engine ID for OpenSSL engine 237 * 238 * "opensc" to select OpenSC engine or "pkcs11" to select PKCS#11 239 * engine. 240 * 241 * This is used if private key operations for EAP-TLS are performed 242 * using a smartcard. 243 */ 244 char *engine_id; 245 246 247 /** 248 * key_id - Key ID for OpenSSL engine 249 * 250 * This is used if private key operations for EAP-TLS are performed 251 * using a smartcard. 252 */ 253 char *key_id; 254 255 /** 256 * cert_id - Cert ID for OpenSSL engine 257 * 258 * This is used if the certificate operations for EAP-TLS are performed 259 * using a smartcard. 260 */ 261 char *cert_id; 262 263 /** 264 * ca_cert_id - CA Cert ID for OpenSSL engine 265 * 266 * This is used if the CA certificate for EAP-TLS is on a smartcard. 267 */ 268 char *ca_cert_id; 269 270 /** 271 * ocsp - Whether to use/require OCSP to check server certificate 272 * 273 * 0 = do not use OCSP stapling (TLS certificate status extension) 274 * 1 = try to use OCSP stapling, but not require response 275 * 2 = require valid OCSP stapling response 276 */ 277 int ocsp; 278 }; 279 280 /** 281 * struct eap_peer_config - EAP peer configuration/credentials 282 */ 283 struct eap_peer_config { 284 /** 285 * identity - EAP Identity 286 * 287 * This field is used to set the real user identity or NAI (for 288 * EAP-PSK/PAX/SAKE/GPSK). 289 */ 290 u8 *identity; 291 292 /** 293 * identity_len - EAP Identity length 294 */ 295 size_t identity_len; 296 297 /** 298 * anonymous_identity - Anonymous EAP Identity 299 * 300 * This field is used for unencrypted use with EAP types that support 301 * different tunnelled identity, e.g., EAP-TTLS, in order to reveal the 302 * real identity (identity field) only to the authentication server. 303 * 304 * If not set, the identity field will be used for both unencrypted and 305 * protected fields. 306 * 307 * This field can also be used with EAP-SIM/AKA/AKA' to store the 308 * pseudonym identity. 309 */ 310 u8 *anonymous_identity; 311 312 /** 313 * anonymous_identity_len - Length of anonymous_identity 314 */ 315 size_t anonymous_identity_len; 316 317 u8 *imsi_identity; 318 size_t imsi_identity_len; 319 320 /** 321 * imsi_privacy_key - IMSI privacy key (PEM encoded X.509v3 certificate) 322 * 323 * This field is used with EAP-SIM/AKA/AKA' to encrypt the permanent 324 * identity (IMSI) to improve privacy. The X.509v3 certificate needs to 325 * include a 2048-bit RSA public key and this is from the operator who 326 * authenticates the SIM/USIM. 327 */ 328 char *imsi_privacy_key; 329 330 /** 331 * machine_identity - EAP Identity for machine credential 332 * 333 * This field is used to set the machine identity or NAI for cases where 334 * and explicit machine credential (instead of or in addition to a user 335 * credential (from %identity) is needed. 336 */ 337 u8 *machine_identity; 338 339 /** 340 * machine_identity_len - EAP Identity length for machine credential 341 */ 342 size_t machine_identity_len; 343 344 /** 345 * password - Password string for EAP 346 * 347 * This field can include either the plaintext password (default 348 * option) or a NtPasswordHash (16-byte MD4 hash of the unicode 349 * presentation of the password) if flags field has 350 * EAP_CONFIG_FLAGS_PASSWORD_NTHASH bit set to 1. NtPasswordHash can 351 * only be used with authentication mechanism that use this hash as the 352 * starting point for operation: MSCHAP and MSCHAPv2 (EAP-MSCHAPv2, 353 * EAP-TTLS/MSCHAPv2, EAP-TTLS/MSCHAP, LEAP). 354 * 355 * In addition, this field is used to configure a pre-shared key for 356 * EAP-PSK/PAX/SAKE/GPSK. The length of the PSK must be 16 for EAP-PSK 357 * and EAP-PAX and 32 for EAP-SAKE. EAP-GPSK can use a variable length 358 * PSK. 359 */ 360 u8 *password; 361 362 /** 363 * password_len - Length of password field 364 */ 365 size_t password_len; 366 367 /** 368 * machine_password - Password string for EAP machine credential 369 * 370 * This field is used when machine credential based on username/password 371 * is needed instead of a user credential (from %password). See 372 * %password for more details on the format. 373 */ 374 u8 *machine_password; 375 376 /** 377 * machine_password_len - Length of machine credential password field 378 */ 379 size_t machine_password_len; 380 381 /** 382 * cert - Certificate parameters for Phase 1 383 */ 384 struct eap_peer_cert_config cert; 385 386 /** 387 * phase2_cert - Certificate parameters for Phase 2 388 * 389 * This is like cert, but used for Phase 2 (inside 390 * EAP-TTLS/PEAP/FAST/TEAP tunnel) authentication. 391 */ 392 struct eap_peer_cert_config phase2_cert; 393 394 /** 395 * machine_cert - Certificate parameters for Phase 2 machine credential 396 * 397 * This is like cert, but used for Phase 2 (inside EAP-TEAP tunnel) 398 * authentication with machine credentials (while phase2_cert is used 399 * for user credentials). 400 */ 401 struct eap_peer_cert_config machine_cert; 402 403 /** 404 * eap_methods - Allowed EAP methods 405 * 406 * (vendor=EAP_VENDOR_IETF,method=EAP_TYPE_NONE) terminated list of 407 * allowed EAP methods or %NULL if all methods are accepted. 408 */ 409 struct eap_method_type *eap_methods; 410 411 /** 412 * phase1 - Phase 1 (outer authentication) parameters 413 * 414 * String with field-value pairs, e.g., "peapver=0" or 415 * "peapver=1 peaplabel=1". 416 * 417 * 'peapver' can be used to force which PEAP version (0 or 1) is used. 418 * 419 * 'peaplabel=1' can be used to force new label, "client PEAP 420 * encryption", to be used during key derivation when PEAPv1 or newer. 421 * 422 * Most existing PEAPv1 implementation seem to be using the old label, 423 * "client EAP encryption", and wpa_supplicant is now using that as the 424 * default value. 425 * 426 * Some servers, e.g., Radiator, may require peaplabel=1 configuration 427 * to interoperate with PEAPv1; see eap_testing.txt for more details. 428 * 429 * 'peap_outer_success=0' can be used to terminate PEAP authentication 430 * on tunneled EAP-Success. This is required with some RADIUS servers 431 * that implement draft-josefsson-pppext-eap-tls-eap-05.txt (e.g., 432 * Lucent NavisRadius v4.4.0 with PEAP in "IETF Draft 5" mode). 433 * 434 * include_tls_length=1 can be used to force wpa_supplicant to include 435 * TLS Message Length field in all TLS messages even if they are not 436 * fragmented. 437 * 438 * sim_min_num_chal=3 can be used to configure EAP-SIM to require three 439 * challenges (by default, it accepts 2 or 3). 440 * 441 * result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use 442 * protected result indication. 443 * 444 * fast_provisioning option can be used to enable in-line provisioning 445 * of EAP-FAST credentials (PAC): 446 * 0 = disabled, 447 * 1 = allow unauthenticated provisioning, 448 * 2 = allow authenticated provisioning, 449 * 3 = allow both unauthenticated and authenticated provisioning 450 * 451 * fast_max_pac_list_len=num option can be used to set the maximum 452 * number of PAC entries to store in a PAC list (default: 10). 453 * 454 * fast_pac_format=binary option can be used to select binary format 455 * for storing PAC entries in order to save some space (the default 456 * text format uses about 2.5 times the size of minimal binary format). 457 * 458 * crypto_binding option can be used to control PEAPv0 cryptobinding 459 * behavior: 460 * 0 = do not use cryptobinding (default) 461 * 1 = use cryptobinding if server supports it 462 * 2 = require cryptobinding 463 * 464 * EAP-WSC (WPS) uses following options: pin=Device_Password and 465 * uuid=Device_UUID 466 * 467 * For wired IEEE 802.1X authentication, "allow_canned_success=1" can be 468 * used to configure a mode that allows EAP-Success (and EAP-Failure) 469 * without going through authentication step. Some switches use such 470 * sequence when forcing the port to be authorized/unauthorized or as a 471 * fallback option if the authentication server is unreachable. By 472 * default, wpa_supplicant discards such frames to protect against 473 * potential attacks by rogue devices, but this option can be used to 474 * disable that protection for cases where the server/authenticator does 475 * not need to be authenticated. 476 */ 477 char *phase1; 478 479 /** 480 * phase2 - Phase2 (inner authentication with TLS tunnel) parameters 481 * 482 * String with field-value pairs, e.g., "auth=MSCHAPV2" for EAP-PEAP or 483 * "autheap=MSCHAPV2 autheap=MD5" for EAP-TTLS. "mschapv2_retry=0" can 484 * be used to disable MSCHAPv2 password retry in authentication failure 485 * cases. 486 */ 487 char *phase2; 488 489 /** 490 * machine_phase2 - Phase2 parameters for machine credentials 491 * 492 * See phase2 for more details. 493 */ 494 char *machine_phase2; 495 496 /** 497 * pcsc - Parameters for PC/SC smartcard interface for USIM and GSM SIM 498 * 499 * This field is used to configure PC/SC smartcard interface. 500 * Currently, the only configuration is whether this field is %NULL (do 501 * not use PC/SC) or non-NULL (e.g., "") to enable PC/SC. 502 * 503 * This field is used for EAP-SIM and EAP-AKA. 504 */ 505 char *pcsc; 506 507 /** 508 * otp - One-time-password 509 * 510 * This field should not be set in configuration step. It is only used 511 * internally when OTP is entered through the control interface. 512 */ 513 u8 *otp; 514 515 /** 516 * otp_len - Length of the otp field 517 */ 518 size_t otp_len; 519 520 /** 521 * pending_req_identity - Whether there is a pending identity request 522 * 523 * This field should not be set in configuration step. It is only used 524 * internally when control interface is used to request needed 525 * information. 526 */ 527 int pending_req_identity; 528 529 /** 530 * pending_req_password - Whether there is a pending password request 531 * 532 * This field should not be set in configuration step. It is only used 533 * internally when control interface is used to request needed 534 * information. 535 */ 536 int pending_req_password; 537 538 /** 539 * pending_req_pin - Whether there is a pending PIN request 540 * 541 * This field should not be set in configuration step. It is only used 542 * internally when control interface is used to request needed 543 * information. 544 */ 545 int pending_req_pin; 546 547 /** 548 * pending_req_new_password - Pending password update request 549 * 550 * This field should not be set in configuration step. It is only used 551 * internally when control interface is used to request needed 552 * information. 553 */ 554 int pending_req_new_password; 555 556 /** 557 * pending_req_passphrase - Pending passphrase request 558 * 559 * This field should not be set in configuration step. It is only used 560 * internally when control interface is used to request needed 561 * information. 562 */ 563 int pending_req_passphrase; 564 565 /** 566 * pending_req_sim - Pending SIM request 567 * 568 * This field should not be set in configuration step. It is only used 569 * internally when control interface is used to request needed 570 * information. 571 */ 572 int pending_req_sim; 573 574 /** 575 * pending_req_otp - Whether there is a pending OTP request 576 * 577 * This field should not be set in configuration step. It is only used 578 * internally when control interface is used to request needed 579 * information. 580 */ 581 char *pending_req_otp; 582 583 /** 584 * pending_req_otp_len - Length of the pending OTP request 585 */ 586 size_t pending_req_otp_len; 587 588 /** 589 * pac_file - File path or blob name for the PAC entries (EAP-FAST) 590 * 591 * wpa_supplicant will need to be able to create this file and write 592 * updates to it when PAC is being provisioned or refreshed. Full path 593 * to the file should be used since working directory may change when 594 * wpa_supplicant is run in the background. 595 * Alternatively, a named configuration blob can be used by setting 596 * this to blob://blob_name. 597 */ 598 char *pac_file; 599 600 /** 601 * mschapv2_retry - MSCHAPv2 retry in progress 602 * 603 * This field is used internally by EAP-MSCHAPv2 and should not be set 604 * as part of configuration. 605 */ 606 int mschapv2_retry; 607 608 /** 609 * new_password - New password for password update 610 * 611 * This field is used during MSCHAPv2 password update. This is normally 612 * requested from the user through the control interface and not set 613 * from configuration. 614 */ 615 u8 *new_password; 616 617 /** 618 * new_password_len - Length of new_password field 619 */ 620 size_t new_password_len; 621 622 /** 623 * fragment_size - Maximum EAP fragment size in bytes (default 1398) 624 * 625 * This value limits the fragment size for EAP methods that support 626 * fragmentation (e.g., EAP-TLS and EAP-PEAP). This value should be set 627 * small enough to make the EAP messages fit in MTU of the network 628 * interface used for EAPOL. The default value is suitable for most 629 * cases. 630 */ 631 int fragment_size; 632 633 #define EAP_CONFIG_FLAGS_PASSWORD_NTHASH BIT(0) 634 #define EAP_CONFIG_FLAGS_EXT_PASSWORD BIT(1) 635 #define EAP_CONFIG_FLAGS_MACHINE_PASSWORD_NTHASH BIT(2) 636 #define EAP_CONFIG_FLAGS_EXT_MACHINE_PASSWORD BIT(3) 637 /** 638 * flags - Network configuration flags (bitfield) 639 * 640 * This variable is used for internal flags to describe further details 641 * for the network parameters. 642 * bit 0 = password is represented as a 16-byte NtPasswordHash value 643 * instead of plaintext password 644 * bit 1 = password is stored in external storage; the value in the 645 * password field is the name of that external entry 646 * bit 2 = machine password is represented as a 16-byte NtPasswordHash 647 * value instead of plaintext password 648 * bit 3 = machine password is stored in external storage; the value in 649 * the password field is the name of that external entry 650 */ 651 u32 flags; 652 653 /** 654 * external_sim_resp - Response from external SIM processing 655 * 656 * This field should not be set in configuration step. It is only used 657 * internally when control interface is used to request external 658 * SIM/USIM processing. 659 */ 660 char *external_sim_resp; 661 662 /** 663 * sim_num - User selected SIM identifier 664 * 665 * This variable is used for identifying which SIM is used if the system 666 * has more than one. 667 */ 668 int sim_num; 669 670 /** 671 * openssl_ciphers - OpenSSL cipher string 672 * 673 * This is an OpenSSL specific configuration option for configuring the 674 * ciphers for this connection. If not set, the default cipher suite 675 * list is used. 676 */ 677 char *openssl_ciphers; 678 679 /** 680 * erp - Whether EAP Re-authentication Protocol (ERP) is enabled 681 */ 682 int erp; 683 684 /** 685 * pending_ext_cert_check - External server certificate check status 686 * 687 * This field should not be set in configuration step. It is only used 688 * internally when control interface is used to request external 689 * validation of server certificate chain. 690 */ 691 enum { 692 NO_CHECK = 0, 693 PENDING_CHECK, 694 EXT_CERT_CHECK_GOOD, 695 EXT_CERT_CHECK_BAD, 696 } pending_ext_cert_check; 697 698 int teap_anon_dh; 699 }; 700 701 702 /** 703 * struct wpa_config_blob - Named configuration blob 704 * 705 * This data structure is used to provide storage for binary objects to store 706 * abstract information like certificates and private keys inlined with the 707 * configuration data. 708 */ 709 struct wpa_config_blob { 710 /** 711 * name - Blob name 712 */ 713 char *name; 714 715 /** 716 * data - Pointer to binary data 717 */ 718 u8 *data; 719 720 /** 721 * len - Length of binary data 722 */ 723 size_t len; 724 725 /** 726 * next - Pointer to next blob in the configuration 727 */ 728 struct wpa_config_blob *next; 729 }; 730 731 #endif /* EAP_CONFIG_H */ 732