From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Testing Core Update 118 Date: Tue, 06 Feb 2018 16:30:02 +0000 Message-ID: <1517934602.21272.89.camel@ipfire.org> In-Reply-To: <29B2F501-2E87-4252-BB50-C78107855534@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7609173428559503538==" List-Id: --===============7609173428559503538== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, On Tue, 2018-02-06 at 10:37 +0100, ummeegge wrote: > Hello, > i wanted to ask if it is possible to add the OpenSSL configuration for Open= VPN > ovpn.cnf --> https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dblob;f=3Dconfig= /ovpn/ope > nssl/ovpn.cnf;h=3D40daf2a0a886dd4957df00c3303d3504f8cb0bc0;hb=3Drefs/heads/= core115 > again to Core 118 update ?=20 > Since there are a couple of users in the IPFire forum which reports the same > issue --> https://forum.ipfire.org/viewtopic.php?f=3D16&t=3D19738p112874#p1= 12874 > and --> https://forum.ipfire.org/viewtopic.php?f=3D27&t=3D20180 , it seems > that ovpn.cnf has been missing with the Core 115 update but the ovpnmain.c= gi > changes has been delivered. >=20 > Might be great if we can deliver this file again to complete this patch > otherwise it does not work... Technically this could be done, but the update is already built and on the servers. Not sure if it is worth rebuilding it since this does not seem to be= a pressing issue when this has been around for months. Please send a patch for this again when we have branched Core Update 119. Best, -Michael >=20 >=20 > Am 01.02.2018 um 16:16 schrieb Michael Tremer: > >=20 > > That sounds good. They have their own configuration file format for > > some modules stuff but since we don't intend to use any of that, we > > should be fine here. > >=20 > > Would you update those packages and rebase the branch on next since you > > have already been working on this? Please send this over to Peter for > > review then and let him test the TCP logging capabilities since he was > > the one who required this in the first place. > >=20 >=20 > Did that now and have changed also the topic to here --> https://lists.ipfi= re. > org/pipermail/development/2018-February/004011.html . >=20 >=20 > Best, >=20 > Erik >=20 --===============7609173428559503538== Content-Type: application/pgp-signature Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="signature.asc" MIME-Version: 1.0 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ2dBZEZpRUU1L3JXNWwzR0dl Mnlwa3R4Z0hudy8yK1FDUWNGQWxwNTJBb0FDZ2tRZ0hudy8yK1EKQ1FlUTVRLzlIMHh0WVRKbk1I cGorZy94Z0IwUWVWZTVJbHdUMkVFT0hhbkdWNGEvb1QxWGV4aDNQZDJxYXBzdAp4VFdEVjNWdk1R T2M1V2N1QTllemYxTGd2cStQRytGL1E1cElLOWJTK2JWdWZaUUcxT1NuSzhYZ1lOOEhSWjVzCnc2 VzlKY1NMdGFwK2NvMnl1a2JxT3U3RzZqekphdWR1WUJhUnpvak56SnFnb3l4eDI0QlhiVzBzeUJW SW8xcTkKd3FVNmk5Vk5vWm1GZVFsY0NlU0VMVG5SNTRKTGxIOGdGTDh3TklJeEhYdENxM3pJZHh5 d3doQmR4aitKS3I2KwprdmFRd0dBK3pnaldaNDltYThiUlhpMlJXenVIc01RTGJqdDJidGFCUCtR RlAwRDJHOU83WU9pcXlaZ0xVRFdWCncwdExPOCswRVNjWWxFN1JWSnBNaGZtNHk4ZUJScXhRanFY NExSeDdTYm9iVGg0Q3BnU05hekcrcXlteHBkeGsKdVdIbnhXcGhLcSsvL3BCQzYwZmlBSlZKN2V0 aUxLTUQvcVhmT3dmTk1TMFBKTFhKN1I4OHpQcXk1b01JdkwycgpQdTVva3ozYUZpM1czSGNHakty cFM5ejRMQmlucnJZK1VjVVFhYzBYNno3cVdJRlpGTXhLMUtEME05YUxIQktIClAzTk5HdXVsMk1k RUZYUVhOSklzbEp3MjdIZ3RrV1RZekZqRy9zV3BzMEhjajZ4Nnl1SnpVMGlEY2dpUmVkelEKakhO SDFEajBhc2xjQzg3WDlXRU1nUVVGMTl0Y3krNGhVOWNTM0QvVGxsSzNqZk8yMVVWeEYwQjl6aE5O aFRsSgowMllpZ3JlQ0V2NUw2b3BVWWZNcldYQnF0Skwwcy9wTkZnKy95YnZ3ZGl0L1QyNG5hZTA9 Cj1NNFIyCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo= --===============7609173428559503538==--