From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] package/openvpn: security bump version to 2.7.2
Date: Thu, 23 Apr 2026 08:14:24 +0200 [thread overview]
Message-ID: <20260423061424.47374-1-bernd@kuhls.net> (raw)
https://github.com/OpenVPN/openvpn/blob/v2.7.2/Changes.rst
Fixes CVE-2026-40215 & CVE-2026-35058.
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
package/openvpn/openvpn.hash | 2 +-
package/openvpn/openvpn.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/openvpn/openvpn.hash b/package/openvpn/openvpn.hash
index d01cb73c98..edfd25bfc9 100644
--- a/package/openvpn/openvpn.hash
+++ b/package/openvpn/openvpn.hash
@@ -1,3 +1,3 @@
# Locally calculated after checking signature
-sha256 9858477ec2894a8a672974d8650dcb1af2eeffb468981a2b619f0fa387081167 openvpn-2.7.1.tar.gz
+sha256 9c3e150a595fc9a375221f2fa9f10524a9c064536cf81c96e3ba66c735b86f26 openvpn-2.7.2.tar.gz
sha256 edaef632cbb643e4e7a221717a6c441a4c1a7c918e6e4d56debc3d8739b233f6 COPYRIGHT.GPL
diff --git a/package/openvpn/openvpn.mk b/package/openvpn/openvpn.mk
index 3bc42f2db1..01e19b2627 100644
--- a/package/openvpn/openvpn.mk
+++ b/package/openvpn/openvpn.mk
@@ -4,7 +4,7 @@
#
################################################################################
-OPENVPN_VERSION = 2.7.1
+OPENVPN_VERSION = 2.7.2
OPENVPN_SITE = https://swupdate.openvpn.net/community/releases
OPENVPN_DEPENDENCIES = host-pkgconf libcap-ng
OPENVPN_LICENSE = GPL-2.0
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-04-23 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 6:14 Bernd Kuhls [this message]
2026-04-23 19:01 ` [Buildroot] [PATCH 1/1] package/openvpn: security bump version to 2.7.2 Julien Olivain via buildroot
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=20260423061424.47374-1-bernd@kuhls.net \
--to=bernd@kuhls.net \
--cc=buildroot@buildroot.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