From 45e8e1149027529194982212c804c0468aa01d98 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Sat, 30 May 2020 00:23:54 +0200 Subject: New upstream version 1.24.2 --- docs/libnm/html/NMSetting8021x.html | 36 ++++++++++++++++++++++-------------- docs/libnm/html/index.html | 2 +- docs/libnm/html/usage.html | 2 +- 3 files changed, 24 insertions(+), 16 deletions(-) (limited to 'docs/libnm/html') diff --git a/docs/libnm/html/NMSetting8021x.html b/docs/libnm/html/NMSetting8021x.html index 4413b405..8b128c86 100644 --- a/docs/libnm/html/NMSetting8021x.html +++ b/docs/libnm/html/NMSetting8021x.html @@ -4690,14 +4690,16 @@ global default is not set, the authentication timeout is 25 seconds.

  “ca-cert”                  GBytes *

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, +

Certificate data is specified using a "scheme"; three are currently +supported: blob, path and pkcs11 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.

Setting this property directly is discouraged; use the nm_setting_802_1x_set_ca_cert() function instead.

Owner: NMSetting8021x

@@ -4731,6 +4733,8 @@ is stored on a PKCS#11 token that requires a login.

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.

Owner: NMSetting8021x

Flags: Read / Write

Default value: NULL

@@ -4988,14 +4992,16 @@ wpa_supplicant documentation for more details.

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, +

Certificate data is specified using a "scheme"; three are currently +supported: blob, path and pkcs11 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.

Setting this property directly is discouraged; use the nm_setting_802_1x_set_phase2_ca_cert() function instead.

Owner: NMSetting8021x

@@ -5029,6 +5035,8 @@ is stored on a PKCS#11 token that requires a login.

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.

Owner: NMSetting8021x

Flags: Read / Write

Default value: NULL

diff --git a/docs/libnm/html/index.html b/docs/libnm/html/index.html index 3f5f2452..768b3d1b 100644 --- a/docs/libnm/html/index.html +++ b/docs/libnm/html/index.html @@ -15,7 +15,7 @@

- for libnm 1.24.0 + for libnm 1.24.2 The latest version of this documentation can be found on-line at https://developer.gnome.org/libnm/stable/. diff --git a/docs/libnm/html/usage.html b/docs/libnm/html/usage.html index d7970207..8bf938b5 100644 --- a/docs/libnm/html/usage.html +++ b/docs/libnm/html/usage.html @@ -96,7 +96,7 @@ 

$ cc $(pkg-config --libs --cflags libnm) -o hello-nm hello-nm.c
   $ ./hello-nm
-  NetworkManager version: 1.24.0
+  NetworkManager version: 1.24.2
 
   $

-- cgit 1.3.0-6-gf8a5