From bbae86d3d2997a853ca0365e8eb7a3ca7489ee09 Mon Sep 17 00:00:00 2001 From: Sebastien Bacher Date: Fri, 25 Jan 2019 11:24:41 +0100 Subject: New upstream version 1.15.2 --- docs/libnm-util/html/NMSettingWirelessSecurity.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 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 d080e83b..76b0781b 100644 --- a/docs/libnm-util/html/NMSettingWirelessSecurity.html +++ b/docs/libnm-util/html/NMSettingWirelessSecurity.html @@ -8,7 +8,7 @@ - + @@ -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 @@ -1898,6 +1898,6 @@ Linksys WRT54G) number the keys 1 - 4.

+
Generated by GTK-Doc V1.29 \ No newline at end of file -- cgit 1.3.0-6-gf8a5