From mboxrd@z Thu Jan  1 00:00:00 1970
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] CRL updater: Update script for OpenVPNs CRL
Date: Thu, 15 Feb 2018 07:18:32 +0100
Message-ID: <1518675512.19288.53.camel@ipfire.org>
In-Reply-To: <1518640067.15001.14.camel@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5330422392374941614=="
List-Id: <development.lists.ipfire.org>

--===============5330422392374941614==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello,


Am Mittwoch, den 14.02.2018, 20:27 +0000 schrieb Michael Tremer:
> Hi,
>=20
> On Wed, 2018-02-14 at 14:24 +0100, ummeegge wrote:
> >=20
> > Hi Michael,
> >=20
> > Am Mittwoch, den 14.02.2018, 12:22 +0000 schrieb Michael Tremer:
> >=20
> > >=20
> > > >=20
> > > > >=20
> > > > > What other steps are urgently necessary that we can roll out
> > > > > OpenVPN
> > > > > 2.4? Are the CGI changes necessary or new features?
> > > > there is the need to make the changes for '--script-security'
> > > > and
> > > > to
> > > > add '--ncp-disable' in ovpnmain.cgi.=C2=A0
> > > Okay. I will wait with merging OpenSSL until we have this sorted.
> > Have send the forgotten AES-GCM patch --> https://lists.ipfire.org/
> > pipe
> > rmail/development/2018-February/004063.html would you merge it to
> > openssl-11 if the review is OK, i would pull the chnages then and
> > prepare/send the last ovpnmain.cgi patch ?
> You can work on the other patches independently from this one.

If we leave the AES-GCM patch for the first behind there is not much more to =
do in ovpnmain.cgi .=C2=A0
This directives=C2=A0https://lists.ipfire.org/pipermail/development/2018-Febr=
uary/004085.html should bring=C2=A0
OpenVPN-2.4 to life again.

>=20
> >=20
> > >=20
> > >=20
> > > >=20
> > > >=20
> > > > Also the integration of the directives via update.sh for the
> > > > core
> > > > update needs to be made since a server stop|start do not
> > > > includes
> > > > the
> > > > changes into server.conf.
> > > And this, too.
> > Since there is currently no
> > config/rootfiles/core/config/rootfiles/core
> > directory for openssl-11 should i make one for core 119 (or 120 ?)
> > and
> > add there the commands in update.sh ?
> Please provide that in an extra script. I do not know when this will
> land in a
> Core Update.

OK, where is a good place for this until then ?

Greetings,

Erik




--===============5330422392374941614==--