Mike Lothian

It was the WolfSSL 5.6.6 release, when I remove the above options only TLS 1.3 is exposed

Here's the script I've been using: Built with: HAPROXY_VERSION=2.8.6 LUA_VERSION=5.4.6 WOLFSSL_VERSION=5.6.6 ``` # Keep a note of the current working directory export JENKINS_DIR=$(pwd) export PREFIX=${JENKINS_DIR}/apps/was/haproxy export HAPROXY_BRANCH=${HAPROXY_VERSION:0:3} export OS_MAJOR_VERSION=`sed -rn...

So I think this is just an issue in general when QUIC is enabled, the same seems to happen with OpenSSL too, I'll investigate further

I still have issues with WolfSSL whether QUIC is enabled or not, but OpenSSL has issues with lower TLS versions when QUIC is enabled

> Any update on this? Apologies, I forgot to test with openssl. I switched back to building with OpenSSL for the moment. Nothing was connecting previously with the existing config...

Gentoo bug https://bugs.gentoo.org/931267

Hmm seems it is happening with nodejs 20.12.1 too, I wonder if something has happened in a clang-18.1.x update

I bet it's ninja 1.12.0

gcc version 13.2.1 20240503 (Gentoo 13.2.1_p20240503 p15) works with Nodejs 20.12.1 & 21.1.0 Clang 18.1.5 doesn't build 20.12.1 or 21.1.0 Clang 18.1.3 successfully built 20.12.1 back on 16/04/24 from my...

We only passed in a yaml file where we needed to manipulate the output or delay startup Can I just check, was passing /dev/null before the same as providing: ```...