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-util/html/NMSettingWirelessSecurity.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/libnm-util/html/NMSettingWirelessSecurity.html') diff --git a/docs/libnm-util/html/NMSettingWirelessSecurity.html b/docs/libnm-util/html/NMSettingWirelessSecurity.html index 83a4be08..76b0781b 100644 --- a/docs/libnm-util/html/NMSettingWirelessSecurity.html +++ b/docs/libnm-util/html/NMSettingWirelessSecurity.html @@ -938,7 +938,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.

Since: 0.9.10

@@ -1560,9 +1560,9 @@ encryption protocol

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 -- cgit 1.3.0-6-gf8a5