From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Update to version 2.4.5
Date: Sat, 17 Mar 2018 09:25:25 +0100 [thread overview]
Message-ID: <1521275125.7784.5.camel@ipfire.org> (raw)
In-Reply-To: <1521224188.178881.7.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2239 bytes --]
Hi Michael,
Am Freitag, den 16.03.2018, 18:16 +0000 schrieb Michael Tremer:
> Hi,
>
> yes. I have merged this patch locally already, but I did not push it
> to the next
> repository, yet.
>
> This will come today. Thank you for reminding me.
OK, thanks for merging.
>
> Do you have anything left for this Core Update? I guess we are ready
> to close
> this soon.
I think so. Have currently nothing left for Core 120.
Anyways there are a lots of other changes rest but it is possibly a
good idea to stay tuned with them until the next one or two Core
updates ?
>
> Best,
> -Michael
>
> On Fri, 2018-03-16 at 17:57 +0100, ummeegge wrote:
> >
> > Hi,
> > thought this update might makes sense for Core 120 but am currently
> > not
> > sure if the patch delivering cycle is meanwhile off ? Since this
> > version do includes also some OpenSSL-1.1 optimizations i thought
> > it
> > might be good to deliver it for the Core 120 release.
> >
> > Best,
> >
> > Erik
> >
> >
> > Am Montag, den 12.03.2018, 13:47 +0100 schrieb Erik Kapfer:
> > >
> > > This is primarily a maintenance release, with further improved
> > > OpenSSL 1.1 integration, several minor bug fixes and other minor
> > > improvements.
> > > Further information can be found in here https://github.com/OpenV
> > > PN/o
> > > penvpn/blob/release/2.4/Changes.rst#version-245 and
> > > here https://community.openvpn.net/openvpn/wiki/ChangesInOpenvpn2
> > > 4 .
> > >
> > > Signed-off-by: Erik Kapfer <erik.kapfer(a)ipfire.org>
> > > ---
> > > lfs/openvpn | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/lfs/openvpn b/lfs/openvpn
> > > index ef25c25..5bd9da7 100644
> > > --- a/lfs/openvpn
> > > +++ b/lfs/openvpn
> > > @@ -24,7 +24,7 @@
> > >
> > > include Config
> > >
> > > -VER = 2.4.4
> > > +VER = 2.4.5
> > >
> > > THISAPP = openvpn-$(VER)
> > > DL_FILE = $(THISAPP).tar.xz
> > > @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> > >
> > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> > >
> > > -$(DL_FILE)_MD5 = 7a2002aad1671b24457bc9432a0c5c52
> > > +$(DL_FILE)_MD5 = c510ad3c8fce738c678dbcc54367c945
> > >
> > > install : $(TARGET)
> > >
Best,
Erik
next prev parent reply other threads:[~2018-03-17 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 12:47 Erik Kapfer
2018-03-16 16:57 ` ummeegge
2018-03-16 18:16 ` Michael Tremer
2018-03-17 8:18 ` Matthias Fischer
2018-03-17 14:32 ` Michael Tremer
2018-03-17 8:25 ` ummeegge [this message]
2018-03-17 14:32 ` Michael Tremer
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=1521275125.7784.5.camel@ipfire.org \
--to=ummeegge@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