Hi Alex,

Nothing stands out as odd in the configuration. There could be an issue in how the application is handling the wolfSSL context.

Have you reviewed the examples repository? In particular this one may be of interest to you:
https://github.com/wolfSSL/wolfssl-exam … blocking.c

Thanks,
Eric @ wolfSSL Support

Yes, the sizeof operator returns the actual size of the buffer, not the string. You want to use

 strlen(buffer)

#ifndef WOLFSSL_USER_SETTINGS
#include <wolfssl/options.h>
#endif
#include <wolfssl/wolfcrypt/settings.h>
#include <wolfssl/ssl.h>
#include <wolfssl/wolfcrypt/sha256.h>
#include <wolfssl/wolfcrypt/error-crypt.h>

void main() {
    byte md5sum[MD5_DIGEST_SIZE]; 
    byte sha256sum[SHA256_DIGEST_SIZE]; 
    byte buffer[1024] = "Hello";
    Md5 md5;
    Sha256 sha256;
    
    //MD5
    wc_InitMd5(&md5);
    wc_Md5Update(&md5, buffer, strlen(buffer));
    wc_Md5Final(&md5, md5sum);
    printf("MD5 is \n");
    for(int i=0 ; i < MD5_DIGEST_SIZE ;i++)  printf("%x",md5sum[i]);
        printf(" \n");
    wc_Md5Free(&md5);


    //SHA256
    wc_InitSha256(&sha256);
    wc_Sha256Update(&sha256, buffer, strlen(buffer));
    wc_Sha256Final(&sha256, sha256sum);
    printf("SHA is \n");
    for(int i=0 ; i < SHA256_DIGEST_SIZE  ;i++) printf("%x",sha256sum[i]);
        printf(" \n");
    wc_Sha256Free(&sha256);
}

HI Kelvin,

Thanks for confirming the fix. Most customers of wolfSSL utilize the ZenDesk platform by emailing `support@wolfssl.com`. Tickets in ZenDesk are monitored and more closely tracked.

You are welcome to use whichever method suits you.

Hello Kelvin,

GitHub is also a public facing platform. If there are issues you would prefer to keep more private, you can also send a message to support@wolfssl.com, which will create a ticket in our ZenDesk issue tracker.

Kind regards,
Eric @ wolfSSL Support

Hi Kelvin,

Thanks again for your excellent report on this issue. I created a fix here:
https://github.com/wolfSSL/wolfMQTT/pull/240

Please let me know if this also fixes the problem from your perspective.

Thanks,
Eric @wolfSSL Support

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