From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] dhcpcd: Update to version 10.0.6 + fix issue experinced by some community users.
Date: Mon, 29 Jan 2024 12:22:18 +0100 [thread overview]
Message-ID: <20240129112218.3257187-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3074 bytes --]
- Update from version 10.0.4 to 10.0.6
- Update of rootfile not required.
- In version 10.0.4 a bug was found
https://github.com/NetworkConfiguration/dhcpcd/issues/260
which was fixed in version 10.0.5. From the community forum it looks like some people
have experienced this issue with the update to 10.0.4 in CU182
https://community.ipfire.org/t/core-update-182-aarch64-red0-interface-stops/10827
- According to the dhcpcd issue report this problem can affect both x86_64 and aarch64
but it seems to affect aarch64 systems much more often and the reports in the community
forum are related to aarch64.
- This patch updates to version 10.0.6 because that is the current latest version and
includes the fix commits for the above issue that were built into 10.0.5
- Changelog
10.0.6
privsep: Stop proxying stderr to console and fix some detachment issues
non-privsep: Fix launcher hangup
DHCP6: Allow the invalid interface name - to mean don't assign an address
from a delegated prefix
DHCP6: Load the configuration for the interface being activated from prefix
delegation
10.0.5
DHCP: re-enter DISCOVER phase if server doesn't reply to our REQUEST
privsep: Allow __NR_dup3 syscall as some libc's use that instead of the dup2
dhcpcd uses
dev: Fix an issue where not opening the dev plugin folder if configured
returned the wrong fd
privsep: Harden the launcher process detecting daemonisation.
compat: arc4random uses explicit_bzero if available
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/dhcpcd | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/dhcpcd b/lfs/dhcpcd
index da832046a..4a2368562 100644
--- a/lfs/dhcpcd
+++ b/lfs/dhcpcd
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2024 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 10.0.4
+VER = 10.0.6
THISAPP = dhcpcd-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 770ee398eccff20cd4a37f89b841f8d580d9a42b456d93673ab3bf6ddf1ed0e49feda47ea8c1206a8a8582bccde80f45c3efbf2e1d0e493b06f04e2c6df876af
+$(DL_FILE)_BLAKE2 = 4afd08cf7377b2262d33bf3f7ac503e081572a7c1ffd53b285842a92d99d88fae44e7e6384134bbe1eb839001f822fa7fb43718c42f9e8e6d11a05ec66fa2fc6
install : $(TARGET)
--
2.43.0
reply other threads:[~2024-01-29 11:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240129112218.3257187-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox