mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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.6 -> 2.6.9
Date: Fri, 15 Mar 2024 05:06:20 +0100	[thread overview]
Message-ID: <20240315040620.725716-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240225151204.54557-5-ahelmcke@ela-soft.com>

Thanks, applied as b9336a85c494f706474e4ca6ed79ebc4f5d90fa7.

Michael

[sent from post-receive hook]

On Fri, 15 Mar 2024 05:06:20 +0100, Andreas Helmcke <ahelmcke@ela-soft.com> wrote:
> various bugfixes, including fixes for CVE-2023-46850 and CVE-2023-46849
> 
> license change completed, therefore the corresponding note in COPYING has been removed
> 
> Full info: https://github.com/OpenVPN/openvpn/releases/tag/v2.6.9
> 
> Signed-off-by: Andreas Helmcke <ahelmcke@ela-soft.com>
> Message-Id: <20240225151204.54557-5-ahelmcke@ela-soft.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/openvpn.make b/rules/openvpn.make
> index 29a4b68e4111..c2cc4fb47458 100644
> --- a/rules/openvpn.make
> +++ b/rules/openvpn.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_OPENVPN) += openvpn
>  #
>  # Paths and names
>  #
> -OPENVPN_VERSION		:= 2.6.6
> -OPENVPN_MD5		:= 660e71db3ed3161e33b4b649855c2477
> +OPENVPN_VERSION		:= 2.6.9
> +OPENVPN_MD5		:= e5beda906a40e997e26766f0de09ecbf
>  OPENVPN			:= openvpn-$(OPENVPN_VERSION)
>  OPENVPN_SUFFIX		:= tar.gz
>  OPENVPN_URL		:= https://github.com/OpenVPN/openvpn/releases/download/v$(OPENVPN_VERSION)/$(OPENVPN).$(OPENVPN_SUFFIX)
> @@ -23,7 +23,7 @@ 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_FILES := \
> -	file://COPYING;md5=d8d34ce6390552676e4ce8279f13c48a \
> +	file://COPYING;md5=4b34e946059f80dcfd811e8dd471b5ed \
>  	file://COPYRIGHT.GPL;md5=52cadf4008002e3c314a47a54fa7306c \
>  	file://src/openvpn/openvpn.c;startline=2;endline=21;md5=b9fb1976bc6d8ad5e02a251351dc58f2 \
>  	file://src/openvpn/base64.c;startline=2;endline=31;md5=f4debd767645b13107fc5912faf2ad8f \



      reply	other threads:[~2024-03-15  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 15:12 [ptxdist] [PATCH] " Andreas Helmcke
2024-03-15  4:06 ` 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=20240315040620.725716-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