wolfSSL provides SSL_CTX_add_server_custom_ext() as a stub which always
returns zero. Do not advertise HAVE_SSL_CTX_ADD_SERVER_CUSTOM_EXT when
building with wolfSSL.
Since
8957622353 ("BUG/MEDIUM: ssl: fix an out-of-bounds read on SSL_CTX
switch with a .sctl file"), the extension is registered on every frontend
context. Calling the stub therefore makes certificate loading fail even
when no .sctl file is present.
Exclude wolfSSL from the capability guard while keeping the OpenSSL
registration unchanged.
Verified an ERR=1 build against wolfSSL 5.7.0, the verifyhost_san VTest,
and live TLS requests using all three certificates from that test.
This must be backported to all supported versions.
#define HAVE_SSL_CLIENT_HELLO_CB
#endif
-#if ((OPENSSL_VERSION_NUMBER >= 0x1000200fL) && !defined(OPENSSL_NO_TLSEXT) && !defined(LIBRESSL_VERSION_NUMBER) && !defined(OPENSSL_IS_BORINGSSL) && !defined(OPENSSL_IS_AWSLC))
+#if ((OPENSSL_VERSION_NUMBER >= 0x1000200fL) && !defined(OPENSSL_NO_TLSEXT) && \
+ !defined(LIBRESSL_VERSION_NUMBER) && !defined(OPENSSL_IS_BORINGSSL) && \
+ !defined(OPENSSL_IS_AWSLC) && !defined(USE_OPENSSL_WOLFSSL))
#define HAVE_SSL_CTX_ADD_SERVER_CUSTOM_EXT
#endif