Great! Glad that helped.

We also have an examples repository that you will find useful. Check out the TLS examples:
https://github.com/wolfSSL/wolfssl-exam … master/tls

Hi Logan,

Welcome to the wolfSSL Forums.

QoS1 messages may be duplicated, this is just part of the standard. If your application needs "once-and-only-once", QoS2 is what you're looking for.

It wasn't clear from your post which side your application is; are you using wolfMQTT as the client, broker. or both?

You should be able to discern if the message is a duplicate by checking the `msg->duplicate` field in the callback when a message is received.

Let us know if that helps.

Thanks,
Eric -wolfSSL Support

Hi Mattia,

That is not expected. If you'd like to create a support ticket, we can review this in more detail. Please send an email to support@wolfssl.com

Thanks,
Eric

Hi den2k

Welcome to the wolfSSL Forums!

Could you tell us a bit about your project using wolfSSL?

RSA is heavy, and RSA 3072 is very heavy!

Couple questions:
Are you building with SP small (WOLFSSL_SP_SMALL)?

Which compiler are you using?

Thanks,

Hi Edoardo,

Thanks for contacting wolfSSL Support. Can you tell from a wireshark inspection which side terminates the connection? Does the client send a corrupted packet that could be causing this?

Thanks,
Eric - wolfSSL Support

Hello Mika,

Which version of wolfSSL are you building? Here is an example config used to run the PQC benchmarks on an STM32F439ZI
https://github.com/wolfSSL/wolfssl/blob … tm32f439zi

Could you tell us a bit about your project using wolfSSL?

Kind regards,
Eric - wolfSSL Support

You can set the cipher list like this:

#define CIPHER_LIST "ECDHE-ECDSA-CHACHA20-POLY1305"

    /* Set cipher list */
    if ((ret = wolfSSL_CTX_set_cipher_list(ctx, CIPHER_LIST))
            != WOLFSSL_SUCCESS) {
        fprintf(stderr, "ERROR: failed to set cipher list\n");
        goto exit;
    }

You can print the available ciphers like this:

static void ShowCiphers(void)
{
    static char ciphers[WOLFSSL_CIPHER_LIST_MAX_SIZE];
    int ret = wolfSSL_get_ciphers(ciphers, (int)sizeof(ciphers));
    if (ret == WOLFSSL_SUCCESS) {
        printf("%s\n", ciphers);
    }
}

Also, it's best to only use one config method, i.e. if you are trying to configure with user settings, do not supply the the other config options in the configure command, add those as defines in the user_settings.h file.

Hi ethanhawkins,

Welcome to the wolfSSL Forums.

QoS 2 requires more round trips between the client and broker. On a lossy network, this could cause problems, but I would expect you'd also see issues with QoS 1 if that were the issue.

Are you using multiple threads? Or non-blocking sockets? Please share some details about the wolfMQTT configuration and the underlying TCP layer.

Could you tell us a bit about your project using wolfMQTT and where you are located for our support records? Feel free to open a support ticket by emailing support@wolfssl.com

Kind regards,
Eric - wolfSSL Support

Hello akr,

Welcome to the wolfSSL Forums.

There are a few ways to accomplish a reduction in the available ciphers. You can configure the library with `--enable-harden-tls`

Alternatively, you can specify the cipher list at run-time using the API `wolfSSL_CTX_set_cipher_list`
Here is an example:
https://github.com/wolfSSL/wolfssl-exam … ls-ecdhe.c

Could you tell us a bit about your project and where you are located for our support records? Please feel free to email us at support@wolfssl.com if you'd prefer to keep that private.

Kind regards,
Eric - wolfSSL

Also, could you please tell us a bit about your wolfMQTT project? We are always interested to hear about how its being used.

Thanks,
Eric

Hi, welcome to the wolfSSL Forums!

That sounds like a feasible approach for managing the cert store. wolfSSL does include a cert manager component:
https://www.wolfssl.com/documentation/m … nager.html

If you have further questions, please feel free to use our support portal by emailing support@wolfssl.com

Kind regards,
Eric - wolfSSL Support