From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] wireguard-tools: Update to version 1.0.20250521
Date: Tue, 24 Jun 2025 23:15:26 +0200 [thread overview]
Message-ID: <20250624211526.2807092-1-adolf.belka@ipfire.org> (raw)
- Update from version 1.0.20210914 to 1.0.20250521
- Update of rootfile not required
- Changelog
1.0.20250521
config: handle strdup failure
wg-quick: linux: add 'dev' to 'ip link add' to avoid keyword conflicts
ipc: add stub for allowedips flags on other platforms
ipc: linux: support incremental allowed ips updates
ipc: freebsd: use AF_LOCAL for the control socket
ipc: linux: enforce IFNAMSIZ limit
man: set private key in PreUp rather than PostUp
wg-quick: run PreUp hook after creating interface
show: fix show all endpoints output
ipc: freebsd: NULL out some freed memory in kernel_set_device()
ipc: freebsd: avoid leaking memory in kernel_get_device()
show: apply const to right part of pointer
ipc: freebsd: move if_wg path to reflect new in-tree location
wg-quick: linux: prevent traffic from momentarily leaking into tunnel
global: dual license core files as MIT for FreeBSD
wg-quick: android: use right regex for host-vs-IP
reresolve-dns: use $EPOCHSECONDS instead of $(date +%s)
embeddable-wg-library: add named wg_endpoint union
ipc: use more clever PnP enumerator
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/wireguard-tools | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/wireguard-tools b/lfs/wireguard-tools
index 5d0e82094..cda5fcddf 100644
--- a/lfs/wireguard-tools
+++ b/lfs/wireguard-tools
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2024 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2025 IPFire Team <info@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 = 1.0.20210914
+VER = 1.0.20250521
THISAPP = wireguard-tools-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -43,7 +43,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 020f4a61597dafc6663e9ee5659f9401416692f5dc8e23afe8d59054bffd32c92814ff2e1f99d6ffe558fdfcf756afc1838e4d425847f892ad4b627a077fe614
+$(DL_FILE)_BLAKE2 = a476720a14e6c547f985d74a9924767d63ce30f09608170858a25cfd98c4762b78cdb9784aa0cee92545424955d4de5bfa932dff7cd852f563656bf6f8d0ad19
install : $(TARGET)
--
2.50.0
reply other threads:[~2025-06-24 21:15 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=20250624211526.2807092-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