From bbae86d3d2997a853ca0365e8eb7a3ca7489ee09 Mon Sep 17 00:00:00 2001
From: Sebastien Bacher
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.