From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Andreas Helmcke <ahelmcke@ela-soft.com>
Subject: Re: [ptxdist] [APPLIED] openvpn: Version bump, 2.6.11 -> 2.7.1
Date: Mon, 18 May 2026 09:53:18 +0200 [thread overview]
Message-ID: <20260518075318.49134-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260424111334.12597-2-ahelmcke@ela-soft.com>
Thanks, applied as 9b5204ce2fccf7429b5a375aad04b39d98363f0d.
Michael
[sent from post-receive hook]
On Mon, 18 May 2026 09:53:18 +0200, Andreas Helmcke <ahelmcke@ela-soft.com> wrote:
> - security fixes: CVE-2024-5594, CVE-2025-13086, CVE-2025-2704
> - various bugfixes and improvements
>
> Link: https://github.com/OpenVPN/openvpn/releases/tag/v2.7.1
>
> License changes: Copyright Year, some URLs, licenses removed for
> software that is only bundled in the Windows client. The text of the GPL
> and the license header in openvpn.c were updated to replace the address
> with the FSF URL. The license of ovpn_dco_linux.h change to BSD-3-Clause
> instead of MIT as one option.
>
> Signed-off-by: Andreas Helmcke <ahelmcke@ela-soft.com>
> Message-Id: <20260424111334.12597-2-ahelmcke@ela-soft.com>
> [mol: fixed license and comment about license changes]
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/openvpn.make b/rules/openvpn.make
> index 475f621e77fc..147dd4465efb 100644
> --- a/rules/openvpn.make
> +++ b/rules/openvpn.make
> @@ -14,20 +14,20 @@ PACKAGES-$(PTXCONF_OPENVPN) += openvpn
> #
> # Paths and names
> #
> -OPENVPN_VERSION := 2.6.11
> -OPENVPN_MD5 := 467b270c54955681add7f253aa03fc5a
> +OPENVPN_VERSION := 2.7.1
> +OPENVPN_MD5 := bec8a86a22304fa70ca6edb5b27c531c
> OPENVPN := openvpn-$(OPENVPN_VERSION)
> OPENVPN_SUFFIX := tar.gz
> OPENVPN_URL := https://github.com/OpenVPN/openvpn/releases/download/v$(OPENVPN_VERSION)/$(OPENVPN).$(OPENVPN_SUFFIX)
> OPENVPN_SOURCE := $(SRCDIR)/$(OPENVPN).$(OPENVPN_SUFFIX)
> OPENVPN_DIR := $(BUILDDIR)/$(OPENVPN)
> -OPENVPN_LICENSE := GPL-2.0-only WITH (openvpn-openssl-exception AND custom-exception) AND BSD-2-Clause AND BSD-3-Clause AND ((GPL-2.0-only WITH Linux-syscall-note) OR MIT)
> +OPENVPN_LICENSE := GPL-2.0-only WITH (openvpn-openssl-exception AND custom-exception) AND BSD-2-Clause AND BSD-3-Clause AND ((GPL-2.0-only WITH Linux-syscall-note) OR BSD-3-Clause)
> OPENVPN_LICENSE_FILES := \
> - file://COPYING;md5=89196bacc47ed37a5b242a535661a049 \
> - file://COPYRIGHT.GPL;md5=52cadf4008002e3c314a47a54fa7306c \
> - file://src/openvpn/openvpn.c;startline=2;endline=21;md5=80aebe6059f2989b52c49783938e7221 \
> + file://COPYING;md5=924af2c382c415a0a68d0d9e7b483d23 \
> + file://COPYRIGHT.GPL;md5=570a9b3749dd0463a1778803b12a6dce \
> + file://src/openvpn/openvpn.c;startline=2;endline=20;md5=13f8f88d2afa15b6ee2cd2642b7c7bd4 \
> file://src/openvpn/base64.c;startline=2;endline=31;md5=f4debd767645b13107fc5912faf2ad8f \
> - file://src/openvpn/ovpn_dco_linux.h;startline=1;endline=1;md5=b317f96dbe63f35baef28266acb68512 \
> + file://src/openvpn/ovpn_dco_linux.h;startline=1;endline=1;md5=65da6a5d2e6f7b92b288c73bb0d968d5 \
> file://src/openvpn/ovpn_dco_freebsd.h;startline=1;endline=1;md5=a7ba62aad20f9685c53b0565a263af30
>
> # ----------------------------------------------------------------------------
> @@ -60,7 +60,8 @@ OPENVPN_CONF_OPT := \
> --disable-lz4 \
> --disable-comp-stub \
> --enable-ofb-cfb \
> - --disable-x509-alt-username \
> + --disable-dns-updown-by-default \
> + --disable-ntlm \
> --disable-plugins \
> --enable-management \
> --disable-pkcs11 \
> @@ -82,6 +83,7 @@ OPENVPN_CONF_OPT := \
> --disable-async-push \
> --disable-wolfssl-options-h \
> --disable-unit-tests \
> + --with-mem-check=no \
> --with-crypto-library=openssl \
> --with-openssl-engine
>
prev parent reply other threads:[~2026-05-18 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 18:23 [ptxdist] [PATCH] " Andreas Helmcke
2026-04-24 9:26 ` Michael Olbrich
2026-04-24 11:13 ` [ptxdist] [PATCH v2] " Andreas Helmcke
2026-05-18 7:53 ` Michael Olbrich [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=20260518075318.49134-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ahelmcke@ela-soft.com \
--cc=ptxdist@pengutronix.de \
/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