From mboxrd@z Thu Jan 1 00:00:00 1970 From: Horace Michael To: development@lists.ipfire.org Subject: Re: [PATCH v2] CRL updater: Update script for OpenVPNs CRL Date: Tue, 13 Feb 2018 08:07:51 +0200 Message-ID: <15716B81-F9B5-4458-9AEC-1EF6DEFAAA20@gmx.com> In-Reply-To: <1518501777.5749.8.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0155668350702493372==" List-Id: --===============0155668350702493372== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, On February 13, 2018 8:02:57 AM GMT+02:00, ummeegge w= rote: >Hi Michael, >thanks for merging. > > >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? > >there is the need to make the changes for '--script-security' and to >add '--ncp-disable' in ovpnmain.cgi.=C2=A0 > Please consider to add auth-nocache also in order to get rid of the warnings = for caching credentials. >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. > >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 ? > >In which core update should this be delivered ? > >Greetings, > >Erik -- Horace Michael (aka H&M) Please excuse my typos and brevity. Sent from a Smartphone.=20 --===============0155668350702493372==--