public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Update to version 2.5.0
Date: Wed, 02 Dec 2020 10:18:38 +0100	[thread overview]
Message-ID: <34d67d3cc3c4152f9b5969b88e0727a37e3c56df.camel@ipfire.org> (raw)
In-Reply-To: <6B927F9D-A014-43C0-B38A-265A0686903D@ipfire.org>

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

Hi Michael,

Am Dienstag, den 01.12.2020, 16:14 +0000 schrieb Michael Tremer:
> Hello Erik,
> 
> This is a massive commit again.
Yes indeed.

> 
> Do you have them broken down somewhere?
Yes shure, i can send them e.g. like sorted in the CGI, e.g. first the
data-cipher{-fallback} selection, second tls-cipher selection and the
last one the authentication ? As an idea.

Have made also a little more progress in here, it is now also possible
to reconfigure the clients which are may updated via a checkbox on =
clients >=2.5.0 and off clients <2.5.0 . So from my side, i think this
very development should be ready.

What currently is missing is a check if 64bit block ciphers are in
usage to print a warning in the WUI that they will be deleted in a near
future but am on it too and this might also be an extra commit...


Best,

Erik

> 
> Best,
> -Michael
> 
> > On 26 Nov 2020, at 19:19, ummeegge <ummeegge(a)ipfire.org> wrote:
> > 
> > Hi Michael,
> > 
> > Am Donnerstag, den 26.11.2020, 12:05 +0000 schrieb Michael Tremer:
> > > Hello,
> > > 
> > > I will leave this one then for the next core update where we
> > > hopefully have moved forward with some of the changes to the UI
> > > and
> > > more people have verified that this won’t break anything :)
> > OK. According to the work on the WUI, i have pushed all i currently
> > have which can be found in here -->
> >  
> > https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=34af1d714178b2cd0c27e8c39052a8c7ce87d116
> > 
> > Best,
> > 
> > Erik
> > 
> > 
> > Best,
> > -Michael
> > 
> > > On 25 Nov 2020, at 23:20, ummeegge <ummeegge(a)ipfire.org> wrote:
> > > 
> > > Hi Michael,
> > > 
> > > Am Mittwoch, den 25.11.2020, 22:43 +0000 schrieb Michael Tremer:
> > > > Hello Erik,
> > > > 
> > > > Am I right to assume that this cannot be merged without
> > > > breaking
> > > > anything?
> > > I think it can be merged without breaking something, two more
> > > already
> > > known warnings are presant with this update here but it broke
> > > nothing.
> > > Tests has been made with 2.4.x clients with a 2.5.0 server but
> > > 2.3.x
> > > clients should be OK with this too. Testings might be important.
> > > 
> > > > 
> > > > Best,
> > > > -Michael
> > > 
> > > Best,
> > > 
> > > Erik
> > > 
> > > > 
> > > > > On 25 Nov 2020, at 22:26, ummeegge <erik.kapfer(a)ipfire.org>
> > > > > wrote:
> > > > > 
> > > > > Signed-off-by: ummeegge <erik.kapfer(a)ipfire.org>
> > > > > ---
> > > > > config/rootfiles/common/openvpn | 1 -
> > > > > lfs/openvpn                     | 4 ++--
> > > > > 2 files changed, 2 insertions(+), 3 deletions(-)
> > > > > 
> > > > > diff --git a/config/rootfiles/common/openvpn
> > > > > b/config/rootfiles/common/openvpn
> > > > > index 547842db3..41ccc885e 100644
> > > > > --- a/config/rootfiles/common/openvpn
> > > > > +++ b/config/rootfiles/common/openvpn
> > > > > @@ -19,7 +19,6 @@ usr/sbin/openvpn
> > > > > #usr/share/doc/openvpn/README.down-root
> > > > > #usr/share/doc/openvpn/README.mbedtls
> > > > > #usr/share/doc/openvpn/management-notes.txt
> > > > > -#usr/share/man/man8/openvpn.8
> > > > > var/ipfire/ovpn/ca
> > > > > var/ipfire/ovpn/caconfig
> > > > > var/ipfire/ovpn/ccd
> > > > > diff --git a/lfs/openvpn b/lfs/openvpn
> > > > > index 779bf5520..b026d515b 100644
> > > > > --- a/lfs/openvpn
> > > > > +++ b/lfs/openvpn
> > > > > @@ -24,7 +24,7 @@
> > > > > 
> > > > > include Config
> > > > > 
> > > > > -VER        = 2.4.9
> > > > > +VER        = 2.5.0
> > > > > 
> > > > > THISAPP    = openvpn-$(VER)
> > > > > DL_FILE    = $(THISAPP).tar.xz
> > > > > @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> > > > > 
> > > > > $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> > > > > 
> > > > > -$(DL_FILE)_MD5 = 446df6dc29364d00929ea9c725412cb8
> > > > > +$(DL_FILE)_MD5 = ba426e2217833b522810d6c06f7cc8f7
> > > > > 
> > > > > install : $(TARGET)
> > > > > 
> > > > > -- 
> > > > > 2.20.1
> > > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> 



      reply	other threads:[~2020-12-02  9:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 22:26 ummeegge
2020-11-25 22:43 ` Michael Tremer
2020-11-25 23:20   ` ummeegge
2020-11-26 12:05     ` Michael Tremer
2020-11-26 19:19       ` ummeegge
2020-11-29 12:42         ` Adolf Belka
2020-12-01 16:13           ` Michael Tremer
2020-12-02 21:31           ` Adolf Belka
2020-12-03 11:27             ` ummeegge
2020-12-01 16:14         ` Michael Tremer
2020-12-02  9:18           ` 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=34d67d3cc3c4152f9b5969b88e0727a37e3c56df.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