1 Reply by embhorn

(1 replies, posted in wolfMQTT)

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

Go to forum: wolfMQTT

2 Reply by embhorn

(5 replies, posted in wolfSSL)

We developed a tool to help optimize the static memory allocations:
https://github.com/wolfSSL/wolfssl-exam … aticmemory

Give it a try!

Go to forum: wolfSSL

3 Reply by embhorn

(5 replies, posted in wolfSSL)

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

Go to forum: wolfSSL

4 Reply by embhorn

(4 replies, posted in wolfCrypt)

Hi den2k,

I think this level of effort will need a proper feature request. I can help you get started if you can send an email to support@wolfssl.com

Thanks,
Eric

Go to forum: wolfCrypt

5 Reply by embhorn

(4 replies, posted in wolfCrypt)

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,

Go to forum: wolfCrypt

6 Reply by embhorn

(2 replies, posted in wolfSSL)

Hi jorgeja,

Welcome to the wolfSSL Forums!

I'll check with the team to see if DTLS is fully supported in our Java wrapper.

Thanks,
Eric - wolfSSL Support

Go to forum: wolfSSL

7 Reply by embhorn

(5 replies, posted in wolfSSL)

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

Go to forum: wolfSSL

8 Reply by embhorn

(1 replies, posted in General Inquiries)

Hi nvbolhuis,

Thanks for contacting wolfSSL Support. We would be interested in learning more about this issue, and perhaps offering some optimizations for your configuration. I'd suggest sending an email to support@wolfssl.com to get started.

Thanks,
Eric - wolfSSL Support

Go to forum: General Inquiries

9 Reply by embhorn

(3 replies, posted in wolfSSL)

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

Go to forum: wolfSSL

10 Reply by embhorn

(10 replies, posted in wolfMQTT)

Hi Neil,

Please open a support ticket by emailing support@wolfssl.com

From there we can better assist you.

Thanks,
Eric - wolfSSL Support

Go to forum: wolfMQTT

11 Reply by embhorn

(10 replies, posted in wolfMQTT)

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);
    }
}

Go to forum: wolfMQTT

12 Reply by embhorn

(10 replies, posted in wolfMQTT)

Hello Neil,

Yes those ciphers are supported wolfSSL v3.9.0. Do you have a packet capture and / or wolfSSL debug log of the succeeding and failing connections?

The server ultimately chooses the cipher suite based on the list sent during the client hello message of the TLS handshake.

Please feel free to open a support ticket by emailing support@wolfssl.com to get more detailed help.

Kind regards,
Eric - wolfSSL Support

Go to forum: wolfMQTT

13 Reply by embhorn

(3 replies, posted in wolfSSL)

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.

Go to forum: wolfSSL

14 Reply by embhorn

(3 replies, posted in wolfSSL)

Hi Robert,

Welcome to the wolfSSL Forums.

That is strange. Could you share the user_settings.h that reproduces this? Which version of wolfSSL are you building?

It might be easier to open a support ticket by emailing support@wolfssl.com

Kind regards,
Eric - wolfSSL Support

Go to forum: wolfSSL

15 Reply by embhorn

(1 replies, posted in wolfMQTT)

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

Go to forum: wolfMQTT

16 Reply by embhorn

(4 replies, posted in wolfSSL)

Hello Mika,

Welcome to the wolfSSL Forums.

wolfSSL has native support for LwIP, so you do not need to set up the IO callbacks. I think that is where your issue is coming from. We actually have an excellent LwIP example that you'll find useful:
https://github.com/wolfSSL/wolfssl-exam … aster/lwip

For LwIP native tcp sockets, define `WOLFSSL_LWIP_NATIVE`
For LwIP sockets API, just use `WOLFSSL_LWIP`

Could you tell us a bit about your project using wolfSSL and where you are from for our support records?

Kind regards,
Eric - wolfSSL Support

Go to forum: wolfSSL

17 Reply by embhorn

(1 replies, posted in wolfSSL)

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

Go to forum: wolfSSL

18 Reply by embhorn

(4 replies, posted in wolfBoot)

Hello mallenbach,

Welcome to the wolfSSL Forums!

Thanks for reaching out. Could you tell us a bit about your wolfBoot project and where you are located for our support statistics?

I am looping in a colleague to help with your question.

Kind regards,
Eric - wolfSSL Support

Go to forum: wolfBoot

19 Reply by embhorn

(2 replies, posted in wolfMQTT)

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

Go to forum: wolfMQTT

20 Reply by embhorn

(2 replies, posted in wolfMQTT)

Hi Alice,

Thanks for contacting wolfSSL Support. Are you publishing from multiple threads? If so you'll need to enable mutex support with the multithread config option
--enable-mt (or define WOLFMQTT_MULTITHREAD)

Could you share the full configuration?

It might be easier for you to submit a support ticket by emailing support@wolfssl.com

Thanks,
Eric

Go to forum: wolfMQTT

21 Reply by embhorn

(1 replies, posted in General Inquiries)

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

Go to forum: General Inquiries

22 Reply by embhorn

(1 replies, posted in wolfSSL)

Hello krcenov,

Welcome to the wolfSSL Forums!

I see you are specifying `-DWOLFSSL_USER_SETTINGS` in the CFLAGS. But you are also adding settings using ./configure. These could be conflicting. We recommend using either the `user_settings.h` header, or `./configure` and generating the options.h header.

Are you including the settings header before any other wolfSSL includes?

Check out our examples repository:
https://github.com/wolfSSL/wolfssl-examples

Specifically:
https://github.com/wolfSSL/wolfssl-exam … callback.c

Can you tell us a bit about yourself and the project you are working on for our support records? Feel free to send an email to support@wolfssl.com for a more private correspondence.

Thanks,
Eric - wolfSSL Support

Go to forum: wolfSSL

23 Reply by embhorn

(4 replies, posted in wolfSSL)

Hi Sunny,

Cert creation form Dilthium keys is not currently supported in wolfCLU. We are working on some PQC cert functionality in wolfCLU. If you'd like to get this specific functionality developed, please send an email to support@wolfssl.com to make a formal feature request.

Thanks,
Eric

Go to forum: wolfSSL

24 Reply by embhorn

(4 replies, posted in wolfSSL)

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

Go to forum: wolfSSL

25 Reply by embhorn

(4 replies, posted in wolfSSL)

Please try adding a define for `WOLFSSL_WC_DILITHIUM`

Go to forum: wolfSSL