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

Hi ClarkS,

Welcome to the wolfSSL Forums. Could you tell us a bit about your project using wolfBoot and where you are located for our support records?

Thanks,
Eric - wolfSSL Support

Hello Max,

Welcome to the wolfSSL Forums. This is a great place to ask your questions. You are also welcome to use our support portal by emailing support@wolfssl.com

Are you building from the Zephyr folder?
https://github.com/wolfSSL/wolfssl/tree/master/zephyr

This uses the user_settings.h file for configuration.
https://github.com/wolfSSL/wolfssl/blob … settings.h

Zephyr should provide the RNG seed:
https://github.com/wolfSSL/wolfssl/blob … 3748-L3776

Thanks,
Eric - wolfSSL Support

Hi fenster

Try enabling the ARM assembler support using `--enable-armasm`

If you need CAAM support, here is a guide:
https://www.wolfssl.com/documentation/m … r-nxp-caam

Thanks,
Eric - wolfSSL Support

Hi Happy,

Thanks for you interest in the wolfCLU project. Did you configure wolfSSL with --enable-crl ?

The CRL parser is capable of handling the command you mentioned:

./wolfssl crl -help
./wolfssl crl
-CAfile <ca file name>
-inform pem or der in format
-in the file to read from
-outform pem or der out format
-out output file to write to
-noout do not print output if set
-text output human readable text of CRL

Hi David,

Welcome to the wolfSSL Forums! Sounds like a very interesting project!

We do support SSL_set_session and SSL_get_session, and a quick look at the OpenSSL code shows that is the buik of the work being done in SSL_copy_session_id.

You could give it a shot at implementing the compatibility API, or if you'd like, you can email us at support@wolfssl.com to open a feature request.

Thanks,
Eric - wolfSSL Support

Hello Happy,

Do you have WOLFSSL_CRL_ALLOW_MISSING_CDP defined in the config, or are you using the callback to override the failure?

If you believe this to be a bug, please email support@wolfssl.com to create a ticket in our support system.

Thanks,
Eric - wolfSSL Support

Since this is a commercial effort, I recommend creating a free presales support ticket by emailing support@wolfssl.com

From there we can help you determine why the broker is sending the alert.

Thanks,
Eric