all: codespell fixes
Codespel run with the same arguments as described in commit58510ed566
('docs: misc. typos pt2'). (cherry picked from commitbf0c4e6ac2
)
This commit is contained in:
8
NEWS
8
NEWS
@@ -17,7 +17,7 @@ USE AT YOUR OWN RISK. NOT RECOMMENDED FOR PRODUCTION USE!
|
||||
* Change default "ipv4.dhcp-client-id" setting for the internal DHCP plugin from
|
||||
"duid" to "mac". This is a change in behavior on upgrade when using the internal
|
||||
DHCP plugin (unless the default is overwritten in "NetworkManager.conf" or specified
|
||||
per connnection profile).
|
||||
per connection profile).
|
||||
* Improve handling of DHCP router options with internal DHCP plugin. For one, accept
|
||||
multiple routers and add a default-route to each. On D-Bus expose the original DNS
|
||||
and NTP servers without cleaning up local nameservers.
|
||||
@@ -28,7 +28,7 @@ USE AT YOUR OWN RISK. NOT RECOMMENDED FOR PRODUCTION USE!
|
||||
with the exception of configuring and showing peers.
|
||||
* Add initrd generator to be used by dracut and use it as new way of handling
|
||||
iBFT.
|
||||
* Deprected "plugins.monitor-connection-files" setting in NetworkManager.conf.
|
||||
* Deprecated "plugins.monitor-connection-files" setting in NetworkManager.conf.
|
||||
This option will have no effect in future versions.
|
||||
* Add AP and Ad-hoc support for iwd Wi-Fi backend.
|
||||
* Warn about invalid settings in "NetworkManager.conf".
|
||||
@@ -44,7 +44,7 @@ and 1.14.6 are also present in NetworkManager-1.14:
|
||||
|
||||
- 1.14.6:
|
||||
* Fix memory corruption in internal DHCPv6 client (CVE-2018-15688).
|
||||
* No longer limit number of search entires in resolv.conf to 6.
|
||||
* No longer limit number of search entries in resolv.conf to 6.
|
||||
* Support restricting NetworkManager.conf device configuration based on used DHCP
|
||||
plugin.
|
||||
* Add "${MAC}" specifier for connection.stable-id. This uses the current MAC
|
||||
@@ -57,7 +57,7 @@ and 1.14.6 are also present in NetworkManager-1.14:
|
||||
systemd-networkd does by default.
|
||||
* Support and use a new kind of secret-key in "/var/lib/NetworkManager/secret_key".
|
||||
The secret-key represents the identity of the machine that is used for various
|
||||
purposes like generating IPv6 stable privacy addesses. It is now combined
|
||||
purposes like generating IPv6 stable privacy addresses. It is now combined
|
||||
with "/etc/machine-id" so that changing only the machine-id results in new identifiers.
|
||||
That matters for example when cloning a virtual machine. Previously, the user
|
||||
hard to prune NetworkManager's secret-key to get a new identity, now regenerating
|
||||
|
@@ -1965,7 +1965,7 @@ _set_fcn_gobject_bytes (ARGS_SET_FCN)
|
||||
g_set_error_literal (error, 1, 0, _("not a valid hex-string"));
|
||||
return FALSE;
|
||||
}
|
||||
/* accept the emtpy word to reset the property to %NULL. */
|
||||
/* accept the empty word to reset the property to %NULL. */
|
||||
goto done;
|
||||
}
|
||||
|
||||
|
@@ -528,7 +528,7 @@ nm_vpn_wireguard_import (const char *filename,
|
||||
|
||||
/* wg-quick accepts the "MTU" value, but it also fetches routes to
|
||||
* autodetect it. NetworkManager won't do that, we can only configure
|
||||
* an explict MTU or no autodetection will be performed. */
|
||||
* an explicit MTU or no autodetection will be performed. */
|
||||
data_mtu = i64;
|
||||
continue;
|
||||
}
|
||||
@@ -581,7 +581,7 @@ nm_vpn_wireguard_import (const char *filename,
|
||||
|| line_match (line, "PreDown", &matched_key, &value)
|
||||
|| line_match (line, "PostUp", &matched_key, &value)
|
||||
|| line_match (line, "PostDown", &matched_key, &value)) {
|
||||
/* we don't run any scripts. Silently ignore these paramters. */
|
||||
/* we don't run any scripts. Silently ignore these parameters. */
|
||||
continue;
|
||||
}
|
||||
|
||||
|
@@ -35,7 +35,7 @@
|
||||
# after activating the profile. Use `nmcli connection up` for that.
|
||||
#
|
||||
# The example script does not support creating or deleting the WireGuard profile itself. It also
|
||||
# does not support modifying other settings of the connection profile, like the IP address configuation.
|
||||
# does not support modifying other settings of the connection profile, like the IP address configuration.
|
||||
# For that also use nmcli. For example:
|
||||
#
|
||||
# PROFILE=wg0
|
||||
|
@@ -217,7 +217,7 @@ nm_wifi_p2p_peer_get_wfd_ies (NMWifiP2PPeer *peer)
|
||||
*
|
||||
* Gets the hardware address of the P2P peer.
|
||||
*
|
||||
* Returns: the hardware adress
|
||||
* Returns: the hardware address
|
||||
*
|
||||
* Since: 1.16
|
||||
**/
|
||||
|
@@ -1184,7 +1184,7 @@ link_config_delayed (NMDeviceWireGuard *self,
|
||||
if (priv->link_config_last_at != 0) {
|
||||
now = nm_utils_get_monotonic_timestamp_ns ();
|
||||
if (now < priv->link_config_last_at + LINK_CONFIG_RATE_LIMIT_NSEC) {
|
||||
/* we ratelimit calls to link_config(), because we call this whenver a resolver
|
||||
/* we ratelimit calls to link_config(), because we call this whenever a resolver
|
||||
* completes. */
|
||||
_LOGT (LOGD_DEVICE, "wireguard link config (%s) (postponed)", reason);
|
||||
priv->link_config_delayed_id = g_timeout_add (NM_MAX ((priv->link_config_last_at + LINK_CONFIG_RATE_LIMIT_NSEC - now) / NM_UTILS_NS_PER_MSEC,
|
||||
@@ -1278,7 +1278,7 @@ _get_dev2_ip_config (NMDeviceWireGuard *self,
|
||||
* a2) an explicit routing table. This is our behavior with "peer-routes" on. In this case
|
||||
* we honor the "ipv4.route-table" and "ipv6.route-table" settings. One difference is that
|
||||
* `wg-quick` would resolve table names from /etc/iproute2/rt_tables. Our connection profiles
|
||||
* only contain table numbers, so that conversion from name to table must have happend
|
||||
* only contain table numbers, so that conversion from name to table must have happened
|
||||
* before already.
|
||||
*
|
||||
* a3) "auto" (the default). In this case, `wg-quick` would only add the route to the
|
||||
@@ -1397,7 +1397,7 @@ get_configured_mtu (NMDevice *device, NMDeviceMtuSource *out_source)
|
||||
* -- despite this being the reality.
|
||||
*
|
||||
* For now, only support configuring an explicit MTU, or leave the setting untouched.
|
||||
* The same limitiation also applies to other "ip-tunnel" types, where we could use
|
||||
* The same limitation also applies to other "ip-tunnel" types, where we could use
|
||||
* similar smarts for autodetecting the MTU.
|
||||
*/
|
||||
return nm_device_get_configured_mtu_from_connection (device,
|
||||
|
@@ -2225,7 +2225,7 @@ supplicant_iface_notify_current_bss (NMSupplicantInterface *iface,
|
||||
}
|
||||
}
|
||||
|
||||
/* We bind the existance of the P2P device to a wifi device that is being
|
||||
/* We bind the existence of the P2P device to a wifi device that is being
|
||||
* managed by NetworkManager and is capable of P2P operation.
|
||||
* Note that some care must be taken here, because we don't want to re-create
|
||||
* the device every time the supplicant interface is destroyed (e.g. due to
|
||||
|
@@ -583,14 +583,14 @@ easy_write_cb (void *buffer, size_t size, size_t nmemb, void *userdata)
|
||||
if (cb_data->concheck.response_good_cnt > (gsize) (100 * 1024)) {
|
||||
/* we expect an empty response. We accept either
|
||||
* 1) status code 204 and any response
|
||||
* 2) status code 200 and an empty reponse.
|
||||
* 2) status code 200 and an empty response.
|
||||
*
|
||||
* Here, we want to continue receiving data, to see whether we have
|
||||
* case 1). Arguably, the server shouldn't send us 204 with a non-empty
|
||||
* response, but we accept that also with a non-empty response, so
|
||||
* keep receiving.
|
||||
*
|
||||
* However, if we get an excessive amound of data, we put a stop on it
|
||||
* However, if we get an excessive amount of data, we put a stop on it
|
||||
* and fail. */
|
||||
cb_data_queue_completed (cb_data,
|
||||
NM_CONNECTIVITY_PORTAL,
|
||||
|
@@ -139,7 +139,7 @@ static GlobalMain gl_main = { };
|
||||
static union {
|
||||
/* a union with an immutable and a mutable alias for the Global.
|
||||
* Since nm-logging must be thread-safe, we must take care at which
|
||||
* places we only read value ("imm") and where we modifiy them ("mut"). */
|
||||
* places we only read value ("imm") and where we modify them ("mut"). */
|
||||
Global mut;
|
||||
const Global imm;
|
||||
} gl = {
|
||||
|
Reference in New Issue
Block a user