Fix typos in wpa_supplicant configuration parameter documentation
Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
660103eca9
commit
205d2d1ff5
2 changed files with 12 additions and 12 deletions
|
@ -181,13 +181,13 @@ struct eap_peer_config {
|
|||
* subject_match - Constraint for server certificate subject
|
||||
*
|
||||
* This substring is matched against the subject of the authentication
|
||||
* server certificate. If this string is set, the server sertificate is
|
||||
* server certificate. If this string is set, the server certificate is
|
||||
* only accepted if it contains this string in the subject. The subject
|
||||
* string is in following format:
|
||||
*
|
||||
* /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@n.example.com
|
||||
*
|
||||
* Note: Since this is a substring match, this cannot be used securily
|
||||
* Note: Since this is a substring match, this cannot be used securely
|
||||
* to do a suffix match against a possible domain name in the CN entry.
|
||||
* For such a use case, domain_suffix_match should be used instead.
|
||||
*/
|
||||
|
@ -198,7 +198,7 @@ struct eap_peer_config {
|
|||
*
|
||||
* Semicolon separated string of entries to be matched against the
|
||||
* alternative subject name of the authentication server certificate.
|
||||
* If this string is set, the server sertificate is only accepted if it
|
||||
* If this string is set, the server certificate is only accepted if it
|
||||
* contains one of the entries in an alternative subject name
|
||||
* extension.
|
||||
*
|
||||
|
|
|
@ -200,7 +200,7 @@ fast_reauth=1
|
|||
#load_dynamic_eap=/usr/lib/wpa_supplicant/eap_md5.so
|
||||
|
||||
# Driver interface parameters
|
||||
# This field can be used to configure arbitrary driver interace parameters. The
|
||||
# This field can be used to configure arbitrary driver interface parameters. The
|
||||
# format is specific to the selected driver interface. This field is not used
|
||||
# in most cases.
|
||||
#driver_param="field=value"
|
||||
|
@ -918,7 +918,7 @@ fast_reauth=1
|
|||
#
|
||||
# Following fields are only used with internal EAP implementation.
|
||||
# eap: space-separated list of accepted EAP methods
|
||||
# MD5 = EAP-MD5 (unsecure and does not generate keying material ->
|
||||
# MD5 = EAP-MD5 (insecure and does not generate keying material ->
|
||||
# cannot be used with WPA; to be used as a Phase 2 method
|
||||
# with EAP-PEAP or EAP-TTLS)
|
||||
# MSCHAPV2 = EAP-MSCHAPv2 (cannot be used separately with WPA; to be used
|
||||
|
@ -1009,16 +1009,16 @@ fast_reauth=1
|
|||
# automatically converted into DH params.
|
||||
# subject_match: Substring to be matched against the subject of the
|
||||
# authentication server certificate. If this string is set, the server
|
||||
# sertificate is only accepted if it contains this string in the subject.
|
||||
# certificate is only accepted if it contains this string in the subject.
|
||||
# The subject string is in following format:
|
||||
# /C=US/ST=CA/L=San Francisco/CN=Test AS/emailAddress=as@example.com
|
||||
# Note: Since this is a substring match, this cannot be used securily to
|
||||
# Note: Since this is a substring match, this cannot be used securely to
|
||||
# do a suffix match against a possible domain name in the CN entry. For
|
||||
# such a use case, domain_suffix_match or domain_match should be used
|
||||
# instead.
|
||||
# altsubject_match: Semicolon separated string of entries to be matched against
|
||||
# the alternative subject name of the authentication server certificate.
|
||||
# If this string is set, the server sertificate is only accepted if it
|
||||
# If this string is set, the server certificate is only accepted if it
|
||||
# contains one of the entries in an alternative subject name extension.
|
||||
# altSubjectName string is in following format: TYPE:VALUE
|
||||
# Example: EMAIL:server@example.com
|
||||
|
@ -1278,13 +1278,13 @@ fast_reauth=1
|
|||
##### Fast Session Transfer (FST) support #####################################
|
||||
#
|
||||
# The options in this section are only available when the build configuration
|
||||
# option CONFIG_FST is set while compiling hostapd. They allow this interface
|
||||
# to be a part of FST setup.
|
||||
# option CONFIG_FST is set while compiling wpa_supplicant. They allow this
|
||||
# interface to be a part of FST setup.
|
||||
#
|
||||
# FST is the transfer of a session from a channel to another channel, in the
|
||||
# same or different frequency bands.
|
||||
#
|
||||
# For detals, see IEEE Std 802.11ad-2012.
|
||||
# For details, see IEEE Std 802.11ad-2012.
|
||||
|
||||
# Identifier of an FST Group the interface belongs to.
|
||||
#fst_group_id=bond0
|
||||
|
|
Loading…
Reference in a new issue