Hi tonyjosi,
My name is Anthony and I am a member of the wolfSSL team.  Let me see if I can look into this for you. I will start by trying to reproduce this.
Warm regards, Anthony

Hi, Thanks for reaching otu Michael.  This appears to be a memory issue.  Can you please try repeating these procedures with Valgrind and then showing us the output?
Warm regards, Anthony

Thanks philipm,
We can continue the conversation there.  The short answer is it is not supported yet.  Please stay tuned to email for a response from support@wolfssl.com.
Warm regards, Anthony

Hi,

As we say in https://github.com/wolfSSL/wolfssl/blob/master/INSTALL:

Use the Visual Studio Solution wolfssl64.sln

Can you tell us a bit about your project?  What are you trying to achieve?

Warm regards, Anthony

Hi Paul,
Please have a look at https://github.com/wolfSSL/wolfssl/tree … DE/ARDUINO .

Can you please let us know a bit about your project?  Is it out of professional, personal or academic interest?  Is there any organization associated with your efforts?

Warm regards, Anthony

Hello dientc.511,
We also have streaming for Gmac and AES-EAX. You can search for the following API

wc_AesEaxInit()
wc_AesEaxEncryptUpdate()
wc_AesEaxEncryptFinal()

What other modes were you looking for?

Warm regards, Anthony

Hi  ja1999,

Thanks for your interest in wolfSSL.  4.8.1 is a very old version.  I suspect you are bumping into expired certificates in our testing directory.

Have you tried a more recent version of wolfSSL-fips-ready?   5.6.4 is the most recent version and it is available at https://wolfssl.com/download . I tested it recently and it works as expected.

Warm regards, Anthony

Hello Again Mattia,

I have successfully imported your ClientHello into wireshark.  It looks to be a compliant TLS 1.3 client hello handshake message.  I see no problems with it.  But then the server sends a DECODE_ERROR alert message. Can you please confirm that the server received the same client hello that you pasted above? I suspect that there is some sort of I/O mishap here.

Warm regards, Anthony

Hi Henrik,

My name is Anthony Hu and I am a member of the wolfSSL team. I see you are using the STM32CubeIDE but do not have wolfSSL.I-CUBE-wolfSSL_conf.h.  In that case you need to enable wolfSSL in the project's .ioc file. Also, when you close the .ioc file, please make sure you tell the IDE to generate code. 

I'm not sure how our zephyr integration works with STM32CubeIDE.  I will consult with my colleagues to learn about this and get back to you.

Warm regards, Anthony

Hello andrea.raiola,

I'm glad to know that you have resolved this on your own.  I have enlisted our cmake expert to have a look at this thread and the stackoverflow link to better understand the issue you are seeing.

Thank you so much for pointing this out to us.

Warm regards, Anthony

Hi Andrea,

My name is Anthony Hu and I am a member of the wolfSSL team.

>  in particulare i get 8368 but in my main.cpp i get 8432.

This is a very big hint.  You can see the definition of

struct RsaKey

in

wolfssl/wolfcrypt/rsa.h 

It varies greatly based on what macros are defined. I noticed you have the following in your C file:

#include <wolfssl/options.h>

Can you please make sure it is exactly the same as the wolfssl/options.h  file in your wolfssl source build directory?

If you would like to further discuss this issue, please open a ticket on our Technical Support system by sending a message to support@wolfssl.com

Warm regards, Anthony

Hi Bahadirmaktav,

How are you today? My name is Anthony Hu and I am a member of the wolfSSL team. I have checked, and we do not support this particular flag in our OpenSSL compatibility layer. However, I will query my colleagues to see if there is a simple way for you to do this. Please stay tuned.

Warm Regards, Anthony