Lines Matching full:used
23 * file should be used since working directory may change when
26 * Alternatively, a named configuration blob can be used by setting
29 * Alternatively, this can be used to only perform matching of the
42 * certificate store (My user account) is used, whereas computer store
43 * (Computer account) is used when running wpasvc as a service.
61 * This field is used with EAP method that use TLS authentication.
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
67 * Alternatively, a named configuration blob can be used by setting
75 * When PKCS#12/PFX file (.p12/.pfx) is used, client_cert should be
78 * used since working directory may change when wpa_supplicant is run
81 * Windows certificate store can be used by leaving client_cert out and
91 * certificate store (My user account) is used, whereas computer store
92 * (Computer account) is used when running wpasvc as a service.
94 * Alternatively, a named configuration blob can be used by setting
116 * Note: Since this is a substring match, this cannot be used securely
118 * For such a use case, domain_suffix_match should be used instead.
142 * It can only be used as per the following example.
177 * If set, this semicolon deliminated list of FQDNs is used as suffix
198 * If set, this FQDN is used as a full match requirement for the
205 * comparison is used, so "Example.com" matches "example.com", but would
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.
230 * This is used if private key operations for EAP-TLS are performed
241 * This is used if private key operations for EAP-TLS are performed
250 * This is used if private key operations for EAP-TLS are performed
258 * This is used if the certificate operations for EAP-TLS are performed
266 * This is used if the CA certificate for EAP-TLS is on a smartcard.
287 * This field is used to set the real user identity or NAI (for
300 * This field is used for unencrypted use with EAP types that support
304 * If not set, the identity field will be used for both unencrypted and
307 * This field can also be used with EAP-SIM/AKA/AKA' to store the
323 * This field is used with EAP-SIM/AKA/AKA' to encrypt the permanent
333 * This field is used to help the EAP-SIM/AKA/AKA' server to identify
334 * the used certificate (and as such, the matching private key). This
343 * This field is used to set the machine identity or NAI for cases where
361 * only be used with authentication mechanism that use this hash as the
365 * In addition, this field is used to configure a pre-shared key for
380 * This field is used when machine credential based on username/password
399 * This is like cert, but used for Phase 2 (inside
407 * This is like cert, but used for Phase 2 (inside EAP-TEAP tunnel)
408 * authentication with machine credentials (while phase2_cert is used
427 * 'peapver' can be used to force which PEAP version (0 or 1) is used.
429 * 'peaplabel=1' can be used to force new label, "client PEAP
430 * encryption", to be used during key derivation when PEAPv1 or newer.
439 * 'peap_outer_success=0' can be used to terminate PEAP authentication
444 * include_tls_length=1 can be used to force wpa_supplicant to include
448 * sim_min_num_chal=3 can be used to configure EAP-SIM to require three
451 * result_ind=1 can be used to enable EAP-SIM and EAP-AKA to use
454 * fast_provisioning option can be used to enable in-line provisioning
461 * fast_max_pac_list_len=num option can be used to set the maximum
464 * fast_pac_format=binary option can be used to select binary format
468 * crypto_binding option can be used to control PEAPv0 cryptobinding
474 * phase2_auth option can be used to control Phase 2 (i.e., within TLS
478 * (private_key/client_cert) is no used and TLS session resumption was
479 * not used (default)
486 * used to configure a mode that allows EAP-Success (and EAP-Failure)
491 * potential attacks by rogue devices, but this option can be used to
502 * be used to disable MSCHAPv2 password retry in authentication failure
517 * This field is used to configure PC/SC smartcard interface.
521 * This field is used for EAP-SIM and EAP-AKA.
528 * This field should not be set in configuration step. It is only used
541 * This field should not be set in configuration step. It is only used
542 * internally when control interface is used to request needed
550 * This field should not be set in configuration step. It is only used
551 * internally when control interface is used to request needed
559 * This field should not be set in configuration step. It is only used
560 * internally when control interface is used to request needed
568 * This field should not be set in configuration step. It is only used
569 * internally when control interface is used to request needed
577 * This field should not be set in configuration step. It is only used
578 * internally when control interface is used to request needed
586 * This field should not be set in configuration step. It is only used
587 * internally when control interface is used to request needed
595 * This field should not be set in configuration step. It is only used
596 * internally when control interface is used to request needed
611 * to the file should be used since working directory may change when
613 * Alternatively, a named configuration blob can be used by setting
621 * This field is used internally by EAP-MSCHAPv2 and should not be set
629 * This field is used during MSCHAPv2 password update. This is normally
646 * interface used for EAPOL. The default value is suitable for most
658 * This variable is used for internal flags to describe further details
674 * This field should not be set in configuration step. It is only used
675 * internally when control interface is used to request external
683 * This variable is used for identifying which SIM is used if the system
693 * list is used.
705 * This field should not be set in configuration step. It is only used
706 * internally when control interface is used to request external
723 * This data structure is used to provide storage for binary objects to store