From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Update to version 2.4.7
Date: Tue, 26 Feb 2019 18:50:35 +0100 [thread overview]
Message-ID: <359d60ea7801f6265a753292f42033a59f2d689a.camel@ipfire.org> (raw)
In-Reply-To: <43D26584-376E-440A-A93E-B4CC199BD47D@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2351 bytes --]
Hi Michael,
On Di, 2019-02-26 at 17:00 +0000, Michael Tremer wrote:
> Thank you. Merged.
Your welcome.
>
> I guess this will also introduce TLS 1.3 for OpenVPN?
Partly yes. As far as i can see (tested also a little) it currently
only introduces TLSv1.3 for the Control Channel via a new directive
called '--tls-ciphersuites' which can also be overviewed with a
openvpn --show-tls
. IPFire currently do not provide a control channel selection for the
ciphers nor a '--tls-min [VER]' option so this update is primarily a
bugfix and a performance one in my opinion but i haven´t had a depper
into it.
I think TLSv1.3 is neverthless not far away for a general usage (data
channel too) on OpenVPN.
Best,
Erik
>
> > On 26 Feb 2019, at 10:56, Erik Kapfer <ummeegge(a)ipfire.org> wrote:
> >
> > 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 2503654f1..61c805fdb 100644
> > --- a/lfs/openvpn
> > +++ b/lfs/openvpn
> > @@ -1,7 +1,7 @@
> > ###################################################################
> > ############
> > #
> > #
> > # IPFire.org - A linux based
> > firewall #
> > -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org>
> > #
> > +# Copyright (C) 2007-2019 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.6
> > +VER = 2.4.7
> >
> > THISAPP = openvpn-$(VER)
> > DL_FILE = $(THISAPP).tar.xz
> > @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> >
> > $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> >
> > -$(DL_FILE)_MD5 = 3a1f3f63bdaede443b4df49957df9405
> > +$(DL_FILE)_MD5 = 4ad8a008e1e7f261b3aa0024e79e7fb7
> >
> > install : $(TARGET)
> >
> > --
> > 2.12.2
> >
>
>
prev parent reply other threads:[~2019-02-26 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 10:56 Erik Kapfer
2019-02-26 17:00 ` Michael Tremer
2019-02-26 17:50 ` ummeegge [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=359d60ea7801f6265a753292f42033a59f2d689a.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