From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] CRL updater: Update script for OpenVPNs CRL
Date: Wed, 14 Feb 2018 12:22:17 +0000
Message-ID: <1518610937.2541.167.camel@ipfire.org>
In-Reply-To: <1518501777.5749.8.camel@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3998635117070463613=="
List-Id: <development.lists.ipfire.org>

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

Hi,

On Tue, 2018-02-13 at 07:02 +0100, ummeegge wrote:
> Hi Michael,
> thanks for merging.
>=20
>=20
> Am Sonntag, den 11.02.2018, 22:25 +0000 schrieb Michael Tremer:
> > Hello,
> >=20
> > I merged this patch into the openssl-11 branch and rebased the
> > branch.
> >=20
> > What other steps are urgently necessary that we can roll out OpenVPN
> > 2.4? Are the CGI changes necessary or new features?
>=20
> there is the need to make the changes for '--script-security' and to
> add '--ncp-disable' in ovpnmain.cgi.=20

Okay. I will wait with merging OpenSSL until we have this sorted.

> 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.

> So there are two steps left for a roll out of a 2.4 minimum version.
> Should i send this in two patches or better in one ?

Please try this in two patches.

> In which core update should this be delivered ?

I am not sure, yet. 119 would have been good, but we already have a lot in th=
ere
and I think we should not delay this too much. But 120 at the latest.

It is really important that we get the latest OpenSSL out there as soon as
possible.

Best,
-Michael

>=20
> Greetings,
>=20
> Erik

--===============3998635117070463613==--