User Tools

Site Tools


networkconfigurationsettings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
networkconfigurationsettings [2020/11/26 18:43]
Andrew Zaborowski Mention EAP-PEAP-Phase2-Method specifically, link to [[ipconfiguration]]
networkconfigurationsettings [2021/01/26 10:26] (current)
Andrew Zaborowski [802.1x (WPA/WPA2 Enterprise) settings]
Line 50: Line 50:
 | ''​EAP-Identity'' ​                                     | //​text// ​                                                                                                                 | EAP identity/​username string transmitted in plaintext. ​ No default, if not provided IWD will request a username at connection time.  See [[https://​tools.ietf.org/​html/​rfc5216#​section-5.2|RFC 5216 Section 5.2]] for requirements on peer identity with regards to client certificate contents. ​ | | ''​EAP-Identity'' ​                                     | //​text// ​                                                                                                                 | EAP identity/​username string transmitted in plaintext. ​ No default, if not provided IWD will request a username at connection time.  See [[https://​tools.ietf.org/​html/​rfc5216#​section-5.2|RFC 5216 Section 5.2]] for requirements on peer identity with regards to client certificate contents. ​ |
 | ''​EAP-TLS-CACert'',​\\ ''​EAP-TTLS-CACert'',​\\ ''​EAP-PEAP-CACert''​ | //file path// or //embedded pem// | Path to a PEM-formatted X.509 root certificate list to use for trust verification,​ both for the server'​s certificate chain and the chain specified with ''​ClientCert''​ (if any).  IWD will require that the root in the verified certificate chains is trusted by at least one CA in the list.  If not provided IWD will have no way to authenticate the server -- discouraged. (optional) | | ''​EAP-TLS-CACert'',​\\ ''​EAP-TTLS-CACert'',​\\ ''​EAP-PEAP-CACert''​ | //file path// or //embedded pem// | Path to a PEM-formatted X.509 root certificate list to use for trust verification,​ both for the server'​s certificate chain and the chain specified with ''​ClientCert''​ (if any).  IWD will require that the root in the verified certificate chains is trusted by at least one CA in the list.  If not provided IWD will have no way to authenticate the server -- discouraged. (optional) |
-| ''​EAP-TLS-ClientCert'',​\\ ''​EAP-TTLS-ClientCert'',​\\ ''​EAP-PEAP-ClientCert'' ​| //file path// or //embedded pem// | Path to a PEM-formatted ​client X.509 certificate or certificate chain to send on server request. ​ For some networks this is mandatory, for others optional. | +| ''​EAP-TLS-ClientCert'',​ | //file path// or //embedded pem// | Path to the client X.509 certificate or certificate chain to send on server request. ​ For some networks this is mandatory, for others optional.  Supported formats include PEM, DER and PKCS#12. | 
-| ''​EAP-TLS-ClientKey'',​\\ ''​EAP-TTLS-ClientKey'',​\\ ''​EAP-PEAP-ClientKey''​ | //file path// or //embedded pem// | Path to a PEM-formatted PKCS #8 private key corresponding to the certified client public key to authenticate ourselves to the server with.  For some networks this is manadatory, for others optional. | +| ''​EAP-TLS-ClientKey''​ | //file path// or //embedded pem// | Path to a private key corresponding to the certified client public key to authenticate ourselves to the server with.  For some networks this is manadatory, for others optional.  Various PEM-based formats and binary PKCS#12 are supported, PKCS#8 is the recommended format. | 
-| ''​EAP-TLS-ClientKeyPassphrase''​,\\ ''​EAP-TTLS-ClientKeyPassphrase''​,\\ ''​EAP-PEAP-ClientKeyPassphrase''​ | //text// | Decryption key for the client private key file.  Must be present iff the private key under ''​ClientKey'' ​is encrypted. |+| ''​EAP-TLS-ClientKeyBundle'' ​| //file path// | Path to a container fail to load both the certificate(s) and the private key from.  Either this or ''​EAP-TLS-ClientCert'' ​''​EAP-TLS-ClientKey''​ can be present but not both.  Supported formats include PKCS#12 and concatenated PEM payloads. | 
 +| ''​EAP-TLS-ClientKeyPassphrase''​ | //text// | Decryption key for the client private key file.  Must be present iff the private key or the certificate ​under one of the three settings above is encrypted. | 
 +''​EAP-TTLS-ClientCert'',​\\ ''​EAP-PEAP-ClientCert'',​\\ ''​EAP-TTLS-ClientKey''​,\\ ''​EAP-PEAP-ClientKey'',​\\ ''​EAP-TTLS-ClientKeyPassphrase'',​\\ ''​EAP-PEAP-ClientKeyPassphrase''​ | //ignored// | Removed in 1.12 |
 | ''​EAP-TLS-ServerDomainMask'',​\\ ''​EAP-TTLS-ServerDomainMask'',​\\ ''​EAP-PEAP-ServerDomainMask''​ | //text// | A mask for the domain names contained in the server'​s certificate. ​ At least one of the domain names present in the certificate'​s Subject Alternative Name extension'​s DNS Name fields or the Common Name has to match at least one mask, or authentication will fail.  Multiple masks can be given separated by semicolons. ​ The masks are split into segments at the dots.  Each segment has to match its corresponding label in the domain name.  An asterisk segment in the mask matches any label. ​ An asterisk segment at the beginning of the mask matches one or more consecutive labels from the beginning of the domain string. | | ''​EAP-TLS-ServerDomainMask'',​\\ ''​EAP-TTLS-ServerDomainMask'',​\\ ''​EAP-PEAP-ServerDomainMask''​ | //text// | A mask for the domain names contained in the server'​s certificate. ​ At least one of the domain names present in the certificate'​s Subject Alternative Name extension'​s DNS Name fields or the Common Name has to match at least one mask, or authentication will fail.  Multiple masks can be given separated by semicolons. ​ The masks are split into segments at the dots.  Each segment has to match its corresponding label in the domain name.  An asterisk segment in the mask matches any label. ​ An asterisk segment at the beginning of the mask matches one or more consecutive labels from the beginning of the domain string. |
 | ''​EAP-TTLS-Phase2-Method''​ | ''​Tunneled-CHAP'',​\\ ''​Tunneled-MSCHAP'',​\\ ''​Tunneled-MSCHAPv2'',​\\ ''​Tunneled-PAP''​ or\\ a valid EAP method name (see ''​EAP-Method''​) | Phase 2 authentication method for EAP-TTLS. ​ Can be either one of the TTLS-specific non-EAP methods (//​Tunneled-//​*),​ or any EAP method documented here.  The following two settings are used if any of the non-EAP methods is used.  No default value. | | ''​EAP-TTLS-Phase2-Method''​ | ''​Tunneled-CHAP'',​\\ ''​Tunneled-MSCHAP'',​\\ ''​Tunneled-MSCHAPv2'',​\\ ''​Tunneled-PAP''​ or\\ a valid EAP method name (see ''​EAP-Method''​) | Phase 2 authentication method for EAP-TTLS. ​ Can be either one of the TTLS-specific non-EAP methods (//​Tunneled-//​*),​ or any EAP method documented here.  The following two settings are used if any of the non-EAP methods is used.  No default value. |
networkconfigurationsettings.1606416193.txt.gz · Last modified: 2020/11/26 18:43 by Andrew Zaborowski