diff options
| author | Sebastien Bacher <seb128@ubuntu.com> | 2020-06-23 18:07:55 +0200 |
|---|---|---|
| committer | Sebastien Bacher <seb128@ubuntu.com> | 2020-06-23 18:09:28 +0200 |
| commit | 2b0b0375d38edd687055f84be895822801618c4a (patch) | |
| tree | acd3aab5044a9bc5950925161b591a08b6e60f53 /docs/api/html/nm-settings.html | |
| parent | 093c9db7b2a46e6042009e703e2e891abd2d2ba3 (diff) | |
| parent | 5ed4e66e01b005212aee22c255c9c6b2a4b040a9 (diff) | |
Merge remote-tracking branch 'salsa/debian/master' into ubuntu/master
Diffstat (limited to 'docs/api/html/nm-settings.html')
| -rw-r--r-- | docs/api/html/nm-settings.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/api/html/nm-settings.html b/docs/api/html/nm-settings.html index 43abfc0c..1e58825e 100644 --- a/docs/api/html/nm-settings.html +++ b/docs/api/html/nm-settings.html @@ -351,7 +351,7 @@ <a name="nm-settings.property.802-1x.ca-cert"></a>ca-cert</td> <td align="left">byte array</td> <td align="left"> </td> -<td>Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td> +<td>Contains the CA certificate if used by the EAP method specified in the "eap" property. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td> </tr> <tr> <td align="left"> @@ -372,7 +372,7 @@ <a name="nm-settings.property.802-1x.ca-path"></a>ca-path</td> <td align="left">string</td> <td align="left"> </td> -<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property.</td> +<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td> </tr> <tr> <td align="left"> @@ -519,7 +519,7 @@ <a name="nm-settings.property.802-1x.phase2-ca-cert"></a>phase2-ca-cert</td> <td align="left">byte array</td> <td align="left"> </td> -<td>Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended.</td> +<td>Contains the "phase 2" CA certificate if used by the EAP method specified in the "phase2-auth" or "phase2-autheap" properties. Certificate data is specified using a "scheme"; three are currently supported: blob, path and pkcs#11 URL. When using the blob scheme this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string "file://" and ending with a terminating NUL byte. This property can be unset even if the EAP method supports CA certificates, but this allows man-in-the-middle attacks and is NOT recommended. Note that enabling NMSetting8021x:system-ca-certs will override this setting to use the built-in path, if the built-in path is not a directory.</td> </tr> <tr> <td align="left"> @@ -540,7 +540,7 @@ <a name="nm-settings.property.802-1x.phase2-ca-path"></a>phase2-ca-path</td> <td align="left">string</td> <td align="left"> </td> -<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property.</td> +<td>UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the "phase2-ca-cert" property. If NMSetting8021x:system-ca-certs is enabled and the built-in CA path is an existing directory, then this setting is ignored.</td> </tr> <tr> <td align="left"> |