On 18/08/2022 22:06, Arne Schwabe wrote:
But if we have to spend time going through support requests and to keep
something maintained that we ourselves have no intrinsic motivation to
support, I will advocate to set/change the status of wolfSSL in OpenVPN
to "unmaintained".
Agreed.
If wolf
Hi Everyone,
this leak has been fixed in wolfSSL in this pull request:
https://github.com/wolfSSL/wolfssl/pull/5514
Sincerely
Juliusz
On 18/08/2022 00:40, Arne Schwabe wrote:
Hey,
currently we still have test failures in wolfSSL in
EVP_PKEY_CTX_new with clang asan. Github action patch that
Am 18.08.22 um 17:21 schrieb Juliusz Sosinowicz:
Hi Arne,
thank you for your report. In the future, please send reports to
supp...@wolfssl.com to guarantee the fastest possible response. This
also helps us track bug reports. I have forwarded this report for you.
Either I or someone else will
Hi Arne,
thank you for your report. In the future, please send reports to
supp...@wolfssl.com to guarantee the fastest possible response. This
also helps us track bug reports. I have forwarded this report for you.
Either I or someone else will investigate this and get back to you with
a solu
Hi,
On Thu, Aug 18, 2022 at 12:40:09AM +0200, Arne Schwabe wrote:
> From 02d4c4d8444188bdf32a054171ea7e20cc7c12ff Mon Sep 17 00:00:00 2001
> From: Arne Schwabe
> Date: Thu, 11 Aug 2022 19:27:12 +0200
> Subject: [PATCH] Add wolfSSL to github actions
>
> I just want to see the world burn a little
Hey,
currently we still have test failures in wolfSSL in
EVP_PKEY_CTX_new with clang asan. Github action patch that reproduces
this also attached. With the OpenVPN 2.6 release coming up in the next
months it would be good if these can be fixed. These look like problems
in the upstream wolfSSL
