public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2 1/2] OpenVPN: Update to version 2.4.9
Date: Thu, 14 May 2020 15:38:39 +0100	[thread overview]
Message-ID: <26DD2230-986A-4150-8344-E7E2F5EC7675@ipfire.org> (raw)
In-Reply-To: <beeb6498ce70047fd4bd257cefb81205c3fe940d.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]

How many people have tested this release?

OpenVPN updates usually come with plenty of regressions, so I would like to make sure that we are not finding those too late and have to halt the release again.

> On 14 May 2020, at 13:40, ummeegge <ummeegge(a)ipfire.org> wrote:
> 
> Hi all,
> just as a reminder, should we release this update too ? This might be
> great cause there are a not so nice crypto bug in the current actual
> version --> 
> https://community.openvpn.net/openvpn/ticket/1228#comment:31 which has
> been fixed in the actual one.

*current or latest is the word you are looking for

-Michael

> 
> Best,
> 
> Erik
> 
> Am Donnerstag, den 07.05.2020, 12:46 +0200 schrieb Erik Kapfer:
>> Beneath several smaller fixes, this version fixes also some OpenSSL
>> problems but also CVE-2020-11810.
>> The full changelog can be found in here 
>> https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn24 .
>> 
>> Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
>> ---
>> lfs/openvpn | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>> 
>> diff --git a/lfs/openvpn b/lfs/openvpn
>> index 0ee437e78..779bf5520 100644
>> --- a/lfs/openvpn
>> +++ b/lfs/openvpn
>> @@ -1,7 +1,7 @@
>> ####################################################################
>> ###########
>> #                                                                   
>>          #
>> # IPFire.org - A linux based
>> firewall                                         #
>> -# Copyright (C) 2007-2019  IPFire Team  <info(a)ipfire.org>           
>>          #
>> +# Copyright (C) 2007-2020  IPFire Team  <info(a)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        = 2.4.8
>> +VER        = 2.4.9
>> 
>> THISAPP    = openvpn-$(VER)
>> DL_FILE    = $(THISAPP).tar.xz
>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>> 
>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>> 
>> -$(DL_FILE)_MD5 = 03a4a077945c157703681a06935bc3f9
>> +$(DL_FILE)_MD5 = 446df6dc29364d00929ea9c725412cb8
>> 
>> install : $(TARGET)
>> 
> 


      reply	other threads:[~2020-05-14 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 16:34 [PATCH] OpenVPN: Add to update and exclude Erik Kapfer
2020-04-17 17:41 ` Michael Tremer
2020-04-17 18:59   ` ummeegge
2020-05-07 10:46 ` [PATCH v2 1/2] OpenVPN: Update to version 2.4.9 Erik Kapfer
2020-05-07 10:46   ` [PATCH v2 2/2] update.sh: Stop|Start OpenVPN for update Erik Kapfer
2020-05-14 12:40   ` [PATCH v2 1/2] OpenVPN: Update to version 2.4.9 ummeegge
2020-05-14 14:38     ` Michael Tremer [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=26DD2230-986A-4150-8344-E7E2F5EC7675@ipfire.org \
    --to=michael.tremer@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