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

Hi Michele,
I am aware that some of our customers call wolfSSL naively from swift.  We have heard no problems from them.  Perhaps you can try it out and if you find any issues, please do let me know.

Warm regards, Anthony

Hi Bluscape.

Just so you know, we accept certificates in both PEM and DER formats.

Here at wolfSSL we love to know what people are doing with our code.  Can you let me understand a bit about yourself, your project and your goals?  Are you doing this as a member of an academic or commercial organization or is it out of personal interest?

Warm regards, Anthony

Hi Michele,

TLS 1.3 is supported and enabled by default for both FiPS and non-FIPS code. Can you please try removing the `-gu` parameters on your execution of `nm`?

> I am attaching my user_seettings.h file

Sorry, but I did not find any attachments on your latest message.  Can you try again?

Warm regards, Anthony

Hi,

currently for iOS we suggest XCode as you have noted in your previous message.  Please see
https://www.wolfssl.com/documentation/m … -x-and-ios as well.  Is swift a requirement?  If so, this conversation would be more appropriate on our support@wolfssl.com alias.  Please send a message there.

Warm regards, Anthony

Hi Kalen, in order to avoid the filter problems, I suggest opening a support ticket instead.  Can you send a clear report to support@wolfssl.com?

I see the 5 0 bytes at the end.  When you use the debugger, does your code that writes in the header, length and content get executed? If not, you need to figure out why.

Warm regards, Anthony

Hi,

I don't see your attachment.

You're probably going to need to run a debugger such as gdb to see if you are actually writing the extension as you expected.

Warm regards, Anthony

Hi Wangzihao,

How are you? We would love to get on a call with you to better understand how you are using wolfSSL. Would you be open to such a call? Don't worry about potential language issues. I can speak Mandarin. Please let me know.

Warm regards, Anthony

Hi Wangzihao,
Thank you very much for using wolfSSL! 

I tried reproducing what you are seeing. Here is what I did :

cd wolfssl
git checkout master
./autogen.sh 
./configure --enable-static --enable-sp-math-all --enable-opensslall
make all
make check 
sudo make install

I then copied the code supplied in your post into a file called `forum.c` and did the following:

g++ forum.cpp /usr/local/lib/libwolfssl.a  -o forum
./forum

Here are the results I got:

get mp_int af: 0
get mp_int bf: 0
get mp_int prime: 0
get mp_int order: 0
get mp_int ra: 0
get mp_int s: 0
get ecc_point pointG: 0
point is on curve: 0
n3*G: 0
n1*G: 0
n2*B: 0
A is equal to C: 0
get mp_int ra1: 0
get mp_int ra2: 0
ra3*G: 0
ra1*G: 0
ra2*E: 0
D is equal to F: -1

Is this what you are seeing as well? 

I will need to confer with my colleagues. Please stay tuned.

Warm regards, Anthony

Hi,
I apologize for not getting you answer more promptly.  I need to go back to my colleagues for this.
Warm regards, Anthony