From bbae86d3d2997a853ca0365e8eb7a3ca7489ee09 Mon Sep 17 00:00:00 2001
From: Sebastien Bacher
The Internet connection is hijacked by a captive
portal gateway. The graphical shell may open a sandboxed web browser window
(because the captive portals typically attempt a man-in-the-middle attacks
- agains the https connections) for the purpose of authenticating to a gateway
+ against the https connections) for the purpose of authenticating to a gateway
and retrigger the connectivity check with CheckConnectivity() when the
browser window is dismissed.
an 802.11 WiFi device
+an 802.11 Wi-Fi device
the device is connecting to the requested network. - This may include operations like associating with the WiFi AP, dialing + This may include operations like associating with the Wi-Fi AP, dialing the modem, connecting to the remote Bluetooth device, etc.
The WiFi network could not be found
+The Wi-Fi network could not be found
NM_ACTIVATION_STATE_FLAG_LIFETIME_BOUND_TO_PROFILE_VISIBILITY
the lifetime + of the activation is bound to the visilibity of the connection profile, + which in turn depends on "connection.permissions" and whether a session + for the user exists. Since: 1.16
+usually, when the connection - has autoconnect enabled and is modified, it becomes elegible to autoconnect + has autoconnect enabled and is modified, it becomes eligible to autoconnect right away. Setting this flag, disables autoconnect until the connection is manually activated.