References: <20200616180046.8069-1-juliusz@...2525...> <4f5787ef-fa03-f7d1-db9a-52fe61caf281@...1227...> <4cb6ea57-4dd1-8230-cec4-d4e8f434944b@...2525...> <5b5bd12b-d2a0-8901-1a0e-4ba7b3e5f7d0@...1227...> <9630aa71-2ba0-879a-3345-85a9551cd169@...2525...> <1e682031-8b10-7beb-1379-b32535f40de8@...1227...> From: David Sommerseth Message-ID: <3c5c4e7d-616a-8992-859b-3bec4f9f83da@...2080...> Date: Fri, 11 Sep 2020 14:29:55 +0200 MIME-Version: 1.0 In-Reply-To: <1e682031-8b10-7beb-1379-b32535f40de8@...1227...> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="97lgZkwInZ1dUSpsZVJL2fzlmAThTsbGX" Subject: Re: [Openvpn-devel] [PATCH] Support for wolfSSL in OpenVPN List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "openvpn-devel@lists.sourceforge.net" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --97lgZkwInZ1dUSpsZVJL2fzlmAThTsbGX Content-Type: multipart/mixed; boundary="8dejEkbQ7lYDBBA1uDVe8UeeDX0hjkaYr"; protected-headers="v1" From: David Sommerseth To: "openvpn-devel@lists.sourceforge.net" Message-ID: <3c5c4e7d-616a-8992-859b-3bec4f9f83da@...2080...> Subject: Re: [Openvpn-devel] [PATCH] Support for wolfSSL in OpenVPN References: <20200616180046.8069-1-juliusz@...2525...> <4f5787ef-fa03-f7d1-db9a-52fe61caf281@...1227...> <4cb6ea57-4dd1-8230-cec4-d4e8f434944b@...2525...> <5b5bd12b-d2a0-8901-1a0e-4ba7b3e5f7d0@...1227...> <9630aa71-2ba0-879a-3345-85a9551cd169@...2525...> <1e682031-8b10-7beb-1379-b32535f40de8@...1227...> In-Reply-To: <1e682031-8b10-7beb-1379-b32535f40de8@...1227...> --8dejEkbQ7lYDBBA1uDVe8UeeDX0hjkaYr Content-Language: en-US Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On 10/09/2020 14:16, Arne Schwabe wrote: > Am 10.09.20 um 14:11 schrieb Juliusz Sosinowicz: >> Hi Arne, >> >> I understand your concern and apologize for the delay. We have been busy >> with the release of wolfSSL 4.5.0. I will make sure that the fixes >> necessary for OpenVPN support will be prioritized. >> >> Sincerely >> Juliusz >=20 > I think the best way forward is to include wolfSSL support into OpenVPN > master now and if we have proper a proper support of wolfSSL that is > kept up to from your side then it will be part of the next release. And > otherwise we remove the support before the next release. That should our > concerns of wanting to see ongoing support and also your concern of it > not being included. I completely agree. This makes a lot of sense and is a reasonable way forw= ard. --=20 kind regards, David Sommerseth OpenVPN Inc --8dejEkbQ7lYDBBA1uDVe8UeeDX0hjkaYr-- --97lgZkwInZ1dUSpsZVJL2fzlmAThTsbGX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCgAGBQJfW23JAAoJEIbPlEyWcf3yFBgQAKUTy5L+t9rvtZI2ada8/5QA rJZN8kmQYEW9CYhC+zMEveoj55YcyhAo9TrRg5Qf3bhB3u11ZSPhaSjtM9raRjDm /f9rHzzDeImw5thNgTUw9XdkJ491E62XwvJL87Ps7WWBFhIEfbWRJAW5MuB59dUI nxJy5IOkdQtD7sHz3mDR0miOfSs2Y1vQADQtVQkVQfr9mKEF+PK2fHqDUyArTu8S YAB/IIVtB5vWbMSE3GG1FkEALxb9XJffwzkDatzefPRJAdVEbiF5V+3Q7Wi45ZwR JvD8cEw0crc1xwE6MK0thF4e0hF9b7XLPMoxHqmp7jEVazV/AOxTC3hbpEpD3S2a equHKWyecp/LajYmWdF+CPlNjQptYpQ19v2j2j0AeFqtli1pVuRriVo1d8C+gi8R 3Xg5AyCd6Hpquk97oIAs6qanfK7ym2b4D8t0FX/54gfza4XiAW+czpEIu+7dIR95 h+UefPyApbzc353M1V5sS8HilSTCyQdAMCgKdrnwl38ebvI3hpbnv21oH80IXSei 2dOKJ4wj4whk+4Ol9cRpMuwq54/SsiR8QCTKlsXMdZKn9jO7hxy88LfJYE0T6TyU bFAwfzkMFF9xPlkbp9J1yJOKai/d7I8ONHOJtIgliGwutW400QZXirdOvUNgnLKc iJnaVtLbakNRJAXNb2qz =NMU6 -----END PGP SIGNATURE----- --97lgZkwInZ1dUSpsZVJL2fzlmAThTsbGX--