Excellent, we'll continue the conversation there!

Hi muataz.m

Thanks for joining the wolfSSL Forums. Perhaps this will be useful:
https://learn.microsoft.com/en-us/xamar … tform/cpp/

If you're interested in having us create a Xamarin Forms port of wolfSSL, please send an email to

facts@wolfssl.com

where we can create a feature request for you.

Thanks,
Eric - wolfSSL Support

Hi Shammon,

Thanks for joining the wolfSSL Forums. Please try including the wolfSSL config header before any other wolfSSL includes:

#ifndef WOLFSSL_USER_SETTINGS
    #include <wolfssl/options.h>
#endif
#include <wolfssl/wolfcrypt/settings.h>

Thanks,
Eric - wolfSSL Support

Hi wangzihao,

Thanks for joining the wolfSSL Forums. Could you share the "./config" command you used?

Are you trying to use the math library directly in your application? If so you'll need to define "WOLFSSL_PUBLIC_MP" in the configuration. You should use the "mp_*" API instead of the direct "sp_*" functions.

Let us know if there are still questions.

Thanks,
Eric - wolfSSL Support

Hello kingutoran98,

We have an example that you might find useful:
https://github.com/wolfSSL/wolfssl-exam … ate_secret

Also this example is a good demonstration of using the x963 API:
https://github.com/wolfSSL/wolfssl-exam … glentest.c

What configuration settings are you building wolfSSL with?

Could you tell us about about your project?

Thanks,
Eric @ wolfSSL Support

Hello Anika,

Yes, releases are always tagged as stable:
https://github.com/wolfSSL/wolfssl/rele … 5.4-stable

Thanks,
Eric - wolfSSL Support

Hi Hodge,

Check out the project instructions from the readme:
https://github.com/wolfSSL/wolfssl/tree … om-scratch

In particular, confirm that the preprocessor macro "WOLFSSL_USER_SETTINGS" is set, per step 15

Thanks,
Eric

Hi senergy,

Thanks for joining the wolfSSL Forums. Using VS Code to build wolfSSL is pretty straightforward. Since you are trying to build for the RPi, you will need to have the right tools to cross compile. VS Code makes setting the target easy. Here is a tutorial that you might find useful:
https://enes-ozturk.medium.com/cross-co … ca4976fdd1

Since you also contacted our support email, we will follow up from there.

Thanks,
Eric - wolfSSL Support

Hi wangzihao,

Thanks for joining the wolfSSL Forums. How did you configure wolfSSL? Have you reviewed the ECC examples in our repository?
https://github.com/wolfSSL/wolfssl-exam … master/ecc

Thanks,
Eric - wolfSSL Support

Are you setting up the callback? Here is an example:
https://github.com/wolfSSL/wolfssl-exam … cryptocb.c

What is the return value from the call to wc_CryptoCb_RegisterDevice ?

Thanks,
Eric @ wolfSSL Support

Hi Sijo,

Thanks for joining the wolfSSL Forums. I'd recommend checking out the wolfSSL example:
https://github.com/wolfSSL/wolfssl/tree/master/tirtos

In particular, you can follow the directions in:
https://github.com/wolfSSL/wolfssl-exam … /README.md

Let us know if there are questions.

Thanks,
Eric, wolfSSL Support

Hello alex23,

Yes, certainly larger keys would take longer to break using brute force.

I recommend trying out the benchmarking utility to help determine the most performant key size / algorithm for your application.
https://github.com/wolfSSL/wolfssl/tree … /benchmark

Thanks,
Eric @ wolfSSL Support