From 9a6dcbf895f9da01768e64b73cec88c16157d91e Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Tue, 26 Mar 2019 23:25:23 +0100 Subject: New upstream version 1.16.0 --- docs/libnm/html/NMSettingWirelessSecurity.html | 30 ++++++++++++++------------ 1 file changed, 16 insertions(+), 14 deletions(-) (limited to 'docs/libnm/html/NMSettingWirelessSecurity.html') diff --git a/docs/libnm/html/NMSettingWirelessSecurity.html b/docs/libnm/html/NMSettingWirelessSecurity.html index 515dabd0..90c77e7c 100644 --- a/docs/libnm/html/NMSettingWirelessSecurity.html +++ b/docs/libnm/html/NMSettingWirelessSecurity.html @@ -6,7 +6,7 @@ - + @@ -21,7 +21,7 @@ Home Up -Prev +Prev Next
@@ -549,8 +549,9 @@ use WEP, LEAP, WPA or WPA2/RSN security

    GEnum
     ├── NMSettingWirelessSecurityFils
     ├── NMSettingWirelessSecurityPmf
-    ├── NMSettingWirelessSecurityWpsMethod
     ╰── NMWepKeyType
+    GFlags
+    ╰── NMSettingWirelessSecurityWpsMethod
     GObject
     ╰── NMSetting
         ╰── NMSettingWirelessSecurity
@@ -970,7 +971,7 @@ algorithm list.

Returns

-

TRUE if the encryption algorith was found and removed; FALSE if it was not.

+

TRUE if the encryption algorithm was found and removed; FALSE if it was not.

@@ -1552,9 +1553,9 @@ nm_setting_wireless_security_get_fils (

enum NMWepKeyType

The NMWepKeyType values specify how any WEP keys present in the setting -are intepreted. There are no standards governing how to hash the various WEP +are interpreted. There are no standards governing how to hash the various WEP key/passphrase formats into the actual WEP key. Unfortunately some WEP keys -can be interpreted in multiple ways, requring the setting to specify how to +can be interpreted in multiple ways, requiring the setting to specify how to interpret the any WEP keys. For example, the key "732f2d712e4a394a375d366931" is both a valid Hexadecimal WEP key and a WEP passphrase. Further, many ASCII keys are also valid WEP passphrases, but since passphrases and ASCII @@ -1666,6 +1667,8 @@ the actual WEP key using the MD5 hash algorithm.

enum NMSettingWirelessSecurityWpsMethod

Configure the use of WPS by a connection while it activates.

+

Note: prior to 1.16, this was a GEnum type instead of a GFlags type +although, with the same numeric values.

Members

@@ -1947,8 +1950,8 @@ list element may be one of "wep40", "wep104", "tkip", or "ccmp".

  “key-mgmt”                 gchar *

Key management used for the connection. One of "none" (WEP), "ieee8021x" (Dynamic WEP), "wpa-none" (Ad-Hoc WPA-PSK), "wpa-psk" (infrastructure -WPA-PSK), or "wpa-eap" (WPA-Enterprise). This property must be set for -any Wi-Fi connection that uses security.

+WPA-PSK), "sae" (SAE) or "wpa-eap" (WPA-Enterprise). +This property must be set for any Wi-Fi connection that uses security.

Flags: Read / Write

Default value: NULL

@@ -2017,12 +2020,11 @@ not specified, both WPA and RSN connections are allowed.

The “psk” property

  “psk”                      gchar *
-

Pre-Shared-Key for WPA networks. If the key is 64-characters long, it -must contain only hexadecimal characters and is interpreted as a -hexadecimal WPA key. Otherwise, the key must be between 8 and 63 ASCII -characters (as specified in the 802.11i standard) and is interpreted as a -WPA passphrase, and is hashed to derive the actual WPA-PSK used when -connecting to the Wi-Fi network.

+

Pre-Shared-Key for WPA networks. For WPA-PSK, it's either an ASCII +passphrase of 8 to 63 characters that is (as specified in the 802.11i +standard) hashed to derive the actual key, or the key in form of 64 +hexadecimal character. The WPA3-Personal networks use a passphrase +of any length for SAE authentication.

Flags: Read / Write

Default value: NULL

-- cgit 1.3.0-6-gf8a5