mtr: upgrade 0.94 -> 0.95
PATCH 1/1 mtr: upgrade 0.94 -> 0.95
0001-Fix-a-lot-of-Werror-format-security-errors-in-printw.patch removed since it is included in 0.95.
---
...ror-format-security-errors-in-printw.patch | 68 -------------------
.../mtr/{mtr_0.94.bb => mtr_0.95.bb} | 6 +-
2 files changed, 2 insertions(+), 72 deletions(-)
delete mode 100644 meta-networking/recipes-support/mtr/mtr/0001-Fix-a-lot-of-Werror-format-security-errors-in-printw.patch
rename meta-networking/recipes-support/mtr/{mtr_0.94.bb => mtr_0.95.bb} (83%)meta-networking/recipes-support/mtr/mtr/0001-Fix-a-lot-of-Werror-format-security-errors-in-printw.patch deleted +0 -68
@@ -1,68 +0,0 @@ -From 628b4b3a16c5e3416aac3eea041ff03375fb495b Mon Sep 17 00:00:00 2001 -From: Khem Raj <[email protected]> -Date: Sat, 30 Oct 2021 11:00:59 -0700 -Subject: [PATCH] Fix a lot of -Werror=format-security errors in - printw/mvprintw - -In all these places a non-constant is used as a format string which -compiler complains about. Fix by using "%s" as format. - -Upstream-Status: Pending - -Signed-off-by: Khem Raj <[email protected]> ---- - ui/curses.c | 10 +++++----- - 1 file changed, 5 insertions(+), 5 deletions(-) - -diff --git a/ui/curses.c b/ui/curses.c -index 34bf30d..c24cf28 100644 ---- a/ui/curses.c -+++ b/ui/curses.c -@@ -432,7 +432,7 @@ static void mtr_curses_hosts( - attron(A_BOLD); - #ifdef HAVE_IPINFO - if (is_printii(ctl)) -- printw(fmt_ipinfo(ctl, addr)); -+ printw("%s", fmt_ipinfo(ctl, addr)); - #endif - if (name != NULL) { - if (ctl->show_ips) -@@ -485,7 +485,7 @@ static void mtr_curses_hosts( - printw("\n "); - #ifdef HAVE_IPINFO - if (is_printii(ctl)) -- printw(fmt_ipinfo(ctl, addrs)); -+ printw("%s", fmt_ipinfo(ctl, addrs)); - #endif - if (name != NULL) { - if (ctl->show_ips) -@@ -650,7 +650,7 @@ static void mtr_curses_graph( - - #ifdef HAVE_IPINFO - if (is_printii(ctl)) -- printw(fmt_ipinfo(ctl, addr)); -+ printw("%s", fmt_ipinfo(ctl, addr)); - #endif - name = dns_lookup(ctl, addr); - printw("%s", name ? name : strlongip(ctl, addr)); -@@ -700,7 +700,7 @@ void mtr_curses_redraw( - - mvprintw(1, 0, "%s (%s) -> %s", ctl->LocalHostname, net_localaddr(), ctl->Hostname); - t = time(NULL); -- mvprintw(1, maxx - 25, iso_time(&t)); -+ mvprintw(1, maxx - 25, "%s", iso_time(&t)); - printw("\n"); - - printw("Keys: "); -@@ -760,7 +760,7 @@ void mtr_curses_redraw( - startstat = padding - 2; - - snprintf(msg, sizeof(msg), " Last %3d pings", max_cols); -- mvprintw(rowstat - 1, startstat, msg); -+ mvprintw(rowstat - 1, startstat, "%s", msg); - - attroff(A_BOLD); - move(rowstat, 0); --- -2.33.1 -
meta-networking/recipes-support/mtr/mtr_0.95.bb renamed from meta-networking/recipes-support/mtr/mtr_0.94.bb +2 -4
@@ -8,10 +8,8 @@ LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \ file://ui/mtr.c;beginline=5;endline=16;md5=00a894a39d53726a27386534d1c4e468" -SRCREV = "2c73cbf4094e4eed343ed11ae5bab2580f3122d1" -SRC_URI = "git://github.com/traviscross/mtr;branch=master;protocol=https \ - file://0001-Fix-a-lot-of-Werror-format-security-errors-in-printw.patch \ - " +SRCREV = "852e5617fbf331cf292723702161f0ac9afe257c" +SRC_URI = "git://github.com/traviscross/mtr;branch=master;protocol=https" S = "${WORKDIR}/git"
Signature · 1 line
2.25.1
PATCH 1/1 networkmanager: upgrade 1.32.12 -> 1.34.0
Changelog:
=========
* initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6".
* core: better handle sd-resolved errors when resolving hostnames.
* nmcli: fix import WireGuard profile with DNS domain and address family disabled.
* ndisc: send router solicitations before expiry.
* policy: send earlier the ip configs to the DNS manager.
* core: support linking with LLD 13.
* wireguard: importing wg-quick configuration files with nmcli
no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself.
* NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters).
* core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon.
* bond: add support for setting queue-id of bond port.
* dns: support configuring DNS over TLS (DoT) with systemd-resolved.
* nmtui: add support for WireGuard profiles.
* nmcli: add aliases nmcli device up|down beside connect|disconnect.
* conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm.
* nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section.
The following changes were backported to 1.32.x releases between 1.32.0 and 1.32.12 are also present in NetworkManager-1.34:
- 1.32.12:
* Fix wrong order of addresses when restarting NetworkManager.
* Preserve the IPv6 ff00::/8 route added by kernel in the local table, necessary for multicast communication.
* Fix emitting the signal for changed metered status of devices.
* Fix applying the ethtool autonegotiation and speed settings.
* initrd: fix crash parsing plain '=' without key.
* cloud-setup: use suppress_prefixlength rule to honor non-default-routes in the main table.
- 1.32.10:
* core: fix the order of IPv6 addresses changing on service restart.
* initrd: add command line option to configure link autonegotiation and speed.
* ifcfg-rh: fix crash when parsing invalid DNS address.
* ifcfg-rh: extend ifup/ifdown scripts to work with connection profile names.
* udev: also react to "move" (and "change") udev actions in our rules.
- 1.32.8:
* firewalld: configure zones on "Reloaded" signal.
* core: fix wrong MTU for bridge interfaces.
* cloud-setup: fix gateway address for Aliyun cloud.
- 1.32.6:
* core: fix adding stale local routes when address changes.
* initrd: tag generated profiles with origin in user data.
* core: introduce "allowed-connections" option to disallow profiles on a device. This allows to filter out profiles that originate from initrd.
* core: introduce "keep-configuration" device option to forcefully activate a profile on start.
* dhcp: handle filename/bootfile_name DHCP option and write it to device state file for initrd/kickstart.
* initrd: add "ib.pkey=" command line option
- 1.32.4:
* core: remove stale entries from "seen-bssids" and "timestamp" files in "/var/lib/NetworkManager".
* bond: support the peer_notif_delay option.
* core: add ipv[46].required-timeout option to wait for IP configuration while activating.
* core: send ARP announcements when there is carrier.
* core: start DHCPv6 when a prefix delegation is needed for shared mode.
* firewall: fix nftables backend to create "ip" table for
IPv4 only.
* initrd: set required-timeout of 20 seconds for default IPv4 configuration to opportunistically wait for IPv4.
* ifcfg: log warning about invalid keys in ifcfg files.
* ifcfg: reject non-UTF-8 from ifcfg files.
* nmcli: show DNS SEARCH field in device information.
* cloud-setup: add support for Aliyun cloud.
- 1.32.2:
* hostname: prefer IPv4 addresses for reverse DNS lookup.
* dhcp: ignore unauthenticated FORCERENEW messages with internal, systemd-based DHCPv4 plugin (CVE-2020-13529). This plugin is not used, unless the undocumented dhcp=systemd option was set.
* cloud-setup: preserve IP addresses, routes and rules from currently active connection profile.
* Various bugfixes and performance improvements.
---
.../{networkmanager_1.32.12.bb => networkmanager_1.34.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-networking/recipes-connectivity/networkmanager/{networkmanager_1.32.12.bb => networkmanager_1.34.0.bb} (98%)meta-networking/recipes-connectivity/networkmanager/networkmanager_1.34.0.bb renamed from meta-networking/recipes-connectivity/networkmanager/networkmanager_1.32.12.bb +1 -1
@@ -27,7 +27,7 @@ SRC_URI = " \ file://0002-Do-not-create-settings-settings-property-documentati.patch \ file://0003-install-firewalld-to-var-libdir-rather-than-hardcod-.patch \ " -SRC_URI[sha256sum] = "a8ab36a0a502fe73cd8e3bacb6585f97fbb94ebef79e276cdbaf11c33ff8f54b" +SRC_URI[sha256sum] = "819795d0899076204f5672421a58f1b1d9e393536ee87bb844b911e6243bf0bd" S = "${WORKDIR}/NetworkManager-${PV}"
Signature · 1 line
2.25.1
PATCH 1/1 cryptsetup: upgrade 2.4.2 -> 2.4.3
In reply to Wang MingyuChangelog:
=========
Stable security bug-fix release that fixes CVE-2021-4122.
All users of cryptsetup 2.4.x must upgrade to this version.
Changes since version 2.4.2
~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Fix possible attacks against data confidentiality through LUKS2 online reencryption extension crash recovery (CVE-2021-4122).
An attacker can modify on-disk metadata to simulate decryption in progress with crashed (unfinished) reencryption step and persistently decrypt part of the LUKS device.
This attack requires repeated physical access to the LUKS device but no knowledge of user passphrases.
The decryption step is performed after a valid user activates the device with a correct passphrase and modified metadata. There are no visible warnings for the user that such recovery happened (except using the luksDump command). The attack can also be reversed afterward (simulating crashed encryption from a plaintext) with possible modification of revealed plaintext.
The size of possible decrypted data depends on configured LUKS2 header size (metadata size is configurable for LUKS2).
With the default parameters (16 MiB LUKS2 header) and only one allocated keyslot (512 bit key for AES-XTS), simulated decryption with checksum resilience SHA1 (20 bytes checksum for 4096-byte blocks), the maximal decrypted size can be over 3GiB.
The attack is not applicable to LUKS1 format, but the attacker can update metadata in place to LUKS2 format as an additional step. For such a converted LUKS2 header, the keyslot area is limited to decrypted size (with SHA1 checksums) over 300 MiB.
The issue is present in all cryptsetup releases since 2.2.0. Versions 1.x, 2.0.x, and 2.1.x are not affected, as these do not contain LUKS2 reencryption extension.
The problem was caused by reusing a mechanism designed for actual reencryption operation without reassessing the security impact for new encryption and decryption operations. While the reencryption requires calculating and verifying both key digests, no digest was needed to initiate decryption recovery if the destination is plaintext (no encryption key). Also, some metadata (like encryption cipher) is not protected, and an attacker could change it. Note that LUKS2 protects visible metadata only when a random change occurs. It does not protect against intentional modification but such modification must not cause a violation of data confidentiality.
The fix introduces additional digest protection of reencryption metadata. The digest is calculated from known keys and critical reencryption metadata. Now an attacker cannot create correct metadata digest without knowledge of a passphrase for used keyslots. For more details, see LUKS2 On-Disk Format Specification version 1.1.0.
The former reencryption operation (without the additional digest) is no longer supported (reencryption with the digest is not backward compatible). You need to finish in-progress reencryption before updating to new packages. The alternative approach is to perform a repair command from the updated package to recalculate reencryption digest and fix metadata.
The reencryption repair operation always require a user passphrase.
WARNING: Devices with older reencryption in progress can be no longer activated without performing the action mentioned above.
Encryption in progress can be detected by running the luksDump command (output includes reencrypt keyslot with reencryption parameters). Also, during the active reencryption, no keyslot operations are available (change of passphrases, etc.).
The issue was found by Milan Broz as cryptsetup maintainer.
Other changes
~~~~~~~~~~~~~
* Add configure option --disable-luks2-reencryption to completely disable LUKS2 reencryption code.
When used, the libcryptsetup library can read metadata with reencryption code, but all reencryption API calls and cryptsetup reencrypt commands are disabled.
Devices with online reencryption in progress cannot be activated. This option can cause some incompatibilities. Please use with care.
* Improve internal metadata validation code for reencryption metadata.
* Add updated documentation for LUKS2 On-Disk Format Specification version 1.1.0 (with reencryption extension description and updated metadata description). See docs/on-disk-format-luks2.pdf or online version in https://gitlab.com/cryptsetup/LUKS2-docs repository.
* Fix support for bitlk (BitLocker compatible) startup key with new metadata entry introduced in Windows 11.
* Fix space restriction for LUKS2 reencryption with data shift. The code required more space than was needed.
---
.../cryptsetup/{cryptsetup_2.4.2.bb => cryptsetup_2.4.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-crypto/cryptsetup/{cryptsetup_2.4.2.bb => cryptsetup_2.4.3.bb} (97%)meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.4.3.bb renamed from meta-oe/recipes-crypto/cryptsetup/cryptsetup_2.4.2.bb +1 -1
@@ -21,7 +21,7 @@ DEPENDS:append:libc-musl = " argp-standalone" LDFLAGS:append:libc-musl = " -largp" SRC_URI = "${KERNELORG_MIRROR}/linux/utils/${BPN}/v${@d.getVar('PV').split('.')[0]}.${@d.getVar('PV').split('.')[1]}/${BP}.tar.xz" -SRC_URI[sha256sum] = "170cc2326a9daeeeb578579176bd10d4a60ee5c4fc5bc69018ce67dafc540b9c" +SRC_URI[sha256sum] = "fc0df945188172264ec5bf1d0bda08264fadc8a3f856d47eba91f31fe354b507" inherit autotools gettext pkgconfig
Signature · 1 line
2.25.1