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

Hi bettylim

Welcome to the wolfSSL forums.

Are you using TLS? Which TCP stack are you using? wolfMQTT does not consume much in the way of resources.

Higher QoS increases the number of round trips required, but does not increase memory usage significantly.

The buffer sizes used should correlate with the average data payload size to optimize memory use. For large payloads, it would be optimal to set it to the TCP driver buffer size.

It would be helpful to discuss your specific project in more detail. Feel free to open a support ticket by emailing support@wolfssl.com

Thanks,
Eric - wolfSSL Support

I'll need to confirm that wolfCLU can handle generating certs with PQC keys

Hello Alex,

Thanks for contacting wolfSSL Support. Can you tell us a bit about your project using wolfBoot? Is this a personal or commercial effort?

I am requesting a review of this topic by our engineers.

Kind regards,
Eric - wolfSSL Support

Hi Rick,

Thanks for joining the wolfSSL Forums. If this is for a commercial project, I suggest contacting our standard support channel by emailing support@wolfssl.com

First off, I would suggest testing a more recent version of the library, as v4.4.0 is quite dated and the issue you are seeing may have been resolved.

Kind regards,
Eric - wolfSSL Support

Hi Bryce,

If you are using fast math, then you need to define FP_MAX_BITS to double the largest key size you intend to use.

So for using RSA 1024 bit keys, define FP_MAX_BITS to 2048

Let us know if that helps.

Thanks,
Eric - wolfSSL Support