From mboxrd@z Thu Jan  1 00:00:00 1970
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: OpenVPN-2.5.0 update procedure and idea collector
Date: Fri, 27 Nov 2020 14:24:23 +0100
Message-ID: <e0f8f2e990d321ee58b66eb34e74839a9ac03708.camel@ipfire.org>
In-Reply-To: <0b611a91-46d1-3732-803c-02d1e795c9e6@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4313776783399452076=="
List-Id: <development.lists.ipfire.org>

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

Am Freitag, den 27.11.2020, 13:40 +0100 schrieb Adolf Belka:
> Hi Erik,
>=20
> I tried downloading your file where the required files are already
> built. However I came up with a different sha256sum to the one you
> had in your file. I downloaded it several times and the same
> difference occurred each time.
That=C2=B4s strange, have had such problems more often...

> I will do the build from scratch.
This might be even better :-)

>=20
> Regards,
>=20
> Adolf.
>=20
>=20
> On 27/11/2020 08:20, ummeegge wrote:
> > Good morning Adolf,
> >=20
> > Am Donnerstag, den 26.11.2020, 23:33 +0100 schrieb Adolf Belka:
> > > Hi Erik,
> > >=20
> > > I take it that I need to take the patch from your repo and apply
> > > it
> > > to my local repo and then build IPFire
> > you would only need to build the OpenVPN binary
> > https://patchwork.ipfire.org/patch/3679/
> > for those of you which can not build it by their own, in here
> > https://people.ipfire.org/~ummeegge/OpenVPN-2.5.0/
> > all files can be found.
> >=20
> > > and install it, and I will then have your version. Should I use
> > > master or next as the base on which to patch it.
> > the files from my repo can be manually installed, please backup up
> > all
> > existing files, the ovpnmain.cgi state is origin/next (incl. the
> > MTU
> > patch from Michael but excluding the up script line for the static-
> > routes for the client N2N).
> > After installation you need to execute 'update-lang-cache' via
> > console
> > that the changes in the language files takes affect.
> > Hit the save button also in the global section since --cipher
> > should be
> > renamed in --data-cipher-fallback...
> > Please check at the beginning that all your old settings are still
> > in
> > place.
> >=20
> > Thanks Adolf.
> >=20
> > Best,
> >=20
> > Erik
> >=20
> > >=20
> > > Thanks,
> > >=20
> > > Adolf.
> > >=20
> > >=20
> > > On 26/11/2020 19:47, ummeegge wrote:
> > > > Hi all,
> > > > for the interested ones, have push the current state to my repo
> > > > which
> > > > can be found in here -->
> > > > =C2=A0=20
> > > > =20
> > > > https://git.ipfire.org/?p=3Dpeople/ummeegge/ipfire-2.x.git;a=3Dcommit=
;h=3D34af1d714178b2cd0c27e8c39052a8c7ce87d116
> > > > feel free to test and criticize it :-) .
> > > >=20
> > > > After integration and configuration, the 'save' button in the
> > > > global
> > > > section should also be pushed since --cipher will replaced by -
> > > > -
> > > > data-
> > > > channel-fallback. For the langs files, a update-lang-cache
> > > > should
> > > > be
> > > > executed via console so the changes can take affect.
> > > >=20
> > > > Happy testing. Best,
> > > >=20
> > > > Erik
> > > >=20
> >=20
> >=20



--===============4313776783399452076==--