Hi Kelvin,

Thanks for living on the bleeding edge of wolfMQTT development! We try to synchronize wolfMQTT releases with wolfSSL, and wolfSSL is currently in testing for a release. Best guess for a wolfMQTT release would be sometime in the next 6 weeks.

Hi Kelvin,

Thanks for your post. We did fix a chunked publish issue since the v1.9.0 release:
https://github.com/wolfSSL/wolfMQTT/pull/230

Would you mind checking with the latest revision from GitHub? If the issue persists, we can open an issue for better tracking.

Thanks,
Eric @ wolfSSL Support

Hi Rusty,

We definitely can help you with a port. Please send a request to facts@wolfssl.com

Thanks,
Eric @ wolfSSL Support

Hi Rusty81,

If you do not need the TLS stack, please try enabling `WOLFCRYPT_ONLY`

Hello raghu,

Have you reviewed the instructions for building wolfSSL with cmake?
https://github.com/wolfSSL/wolfssl/blob … NSTALL#L80

Thanks,
Eric @ wolfSSL Support

Hello beaveryoga,

Thanks for joining the forums. This functionality was added to enable openSSL compatibility. It looks like the proper API is `wolfSSL_CTX_set_tlsext_servername_callback`, which is nearly identical to `wolfSSL_CTX_set_servername_callback`.

I could not find any openSSL examples of using `SSL_CTX_set_servername_callback`. I'll check with the n team to see if there is more info to share.

Thanks,
Eric @ wolfSSL Support

Does your application call `wolfSSL_check_domain_name`? Verifying the common name in the cert is fine, but not necessary if you also have a trusted CA that signed the server's certificate.

Hello a7v7

Could you please send an email referencing this issue to support@wolfssl.com ?

Kind regards,
Eric @ wolfSSL Support

Hi @hablutzel1

Thanks for joining the forum. Would you please send an email to support@wolfssl.com referencing this post? We'd like to get some more information about the issue you are seeing.

Thanks,
Eric @ wolfSSL Support

Okay, there is some issue with filesystem access from the wolfSSL test scripts in MSYS. I can get around it with

#define USE_CERT_BUFFERS_256
#define USE_CERT_BUFFERS_4096
#define NO_WRITE_TEMP_FILES

...added to options.h (or added as CFLAGS during configure).

That allows testsuite.test.exe to pass, but there is a similar issue with unit.test

Thanks for that. By chance do you have any folder names with spaces in the path to the the wolfssl install? MSYS can be finicky with absolute paths.