public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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.20260223
Date: Thu, 30 Apr 2026 16:05:21 +0200	[thread overview]
Message-ID: <20260430140521.3523893-3-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260430140521.3523893-1-adolf.belka@ipfire.org>

- Update from version 1.0.20250521 to 1.0.20260223
- No change in rootfile
- Changelog
1.0.20260223
  * wg-quick: linux: use smallest mtu, not largest
	  The minimum endpoint MTU selection should now actually work.
  * wg-quick: pass on # comments to {Pre,Post}{Up,Down}
	  This handles the case of a literal # being used in a command.
  * wg-quick: linux: deal with resolvconf migration more gracefully
	  This fixes an issue when upgrading Ubuntu boxes.
  * wg-quick: use addconf instead of setconf
	  This will prevent wiping out changes made in PreUp.
  * wg-quick: linux: do not unnecessarily set sysctl
	  Improves docker compatibility.
  * wg-quick at .service: add deps on wg-quick.target
  * config: preserve const correctness
	  Squelches a warning on recent gcc.
  * syncconf: account for psks removed from config file
  * syncconf: account for persistent keepalive removed from config file
	  PersistentKeepalive and PresharedKey will be removed if they're not found in
	  the config file during a syncconf operation.

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 cda5fcddf..f6d392000 100644
--- a/lfs/wireguard-tools
+++ b/lfs/wireguard-tools
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2025  IPFire Team  <info@ipfire.org>                     #
+# Copyright (C) 2007-2026  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.20250521
+VER        = 1.0.20260223
 
 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 = a476720a14e6c547f985d74a9924767d63ce30f09608170858a25cfd98c4762b78cdb9784aa0cee92545424955d4de5bfa932dff7cd852f563656bf6f8d0ad19
+$(DL_FILE)_BLAKE2 = c6352dff6462fd902f545328b66aa7d6f34909b6bd602e80c4186a3234595578132d6c888aa19cb073c7ae8a2d4d213108f7ec0e5a87cc35ed148623bde4decd
 
 install : $(TARGET)
 
-- 
2.54.0



      parent reply	other threads:[~2026-04-30 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 14:05 [PATCH] core 202: Ship wireguard-tools Adolf Belka
2026-04-30 14:05 ` [PATCH] tshark: Update to version 4.6.5 Adolf Belka
2026-04-30 14:05 ` Adolf Belka [this message]

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=20260430140521.3523893-3-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