5.7.4 is outdated, please try upgrading to 5.8.0 and let me know if it helps.

Here is a full code sample which should work:

int main(void) {
    int i;
    int j;
    byte input[] = {255};
    byte hash[48];
    wc_Sha384 sha384;
    for (j = 0; j < 10; j++) {
        wc_InitSha384(&sha384);
        wc_Sha384Update(&sha384, input, sizeof(input));
        wc_Sha384Final(&sha384, hash);
        printf("Buffer: \n");
        for (i = 0; i < 48; i++)
            printf("%02x ", hash[i]);
        printf("\n");
    }
    return 0; 
}

Hi Bryce,

Thanks for the followup.  Looks like you are initializing a different variable "sha" here: wc_InitSha384(&sha);
sha384 must be initialized before you can use it, please try replacing this line with: wc_InitSha384(&sha384);

Thanks,
Kareem

Hello matemagico13,

Thank you for your interest in wolfSSL.  May I ask if you're working on a personal or commercial project?  Are you able to tell us more about your project?  If this information is sensitive, please contact us at support [AT] wolfssl [DOT] com.

Error 127 means command not found, this can mean that your toolchain is unable to find the executable or that it is not marked as executable.  It looks like in this case it is trying to execute the static library directly, which is not valid.
I do see that you've commented out $(SIZE) in the build_static rule, can you elaborate on why you've done this?  Does it work if you uncomment this?

Thanks,
Kareem

Hello Ahmed,

You will need to make a project for wolfSSL in your IDE, build it, then link it with your application.  We have some IDE examples here but we don't currently have any for NXP Design Studio: https://github.com/wolfSSL/wolfssl/tree/master/IDE  We do have an MCUEXPRESSO example for NXP.

To configure wolfSSL, you'll need to place a user_settings.h file with your build settings in the root of the wolfSSL directory, then built with WOLFSSL_USER_SETTINGS defined.  I would recommend referring to our examples here, specifically user_settings_template.h: https://github.com/wolfSSL/wolfssl/tree … es/configs
You may also find the "Building wolfSSL" section of our manual helpful: https://www.wolfssl.com/documentation/m … ter02.html

For our OpenSSL compatibility layer, you'll need to define OPENSSL_EXTRA in your user_settings.h, if you need more APIs which are not covered in extra you can also define OPENSSL_ALL, but this is a more resource-intensive operation.

Can you share some information on your project?  Are you working on a personal or commercial project?  If this information is private, you are welcome to email us at support [AT] wolfssl [DOT] com.

Thanks,
Kareem

Hi fenster,

Great question.  Our wolfssl-py repo includes a client and server example, they both support DTLS using the -u argument.  I would recommend using them as a reference: https://github.com/wolfSSL/wolfssl-py/t … r/examples

Thanks,
Kareem

Hi bkeller02,

I expect the function wc_ChaCha20Poly1305_Decrypt to be available with the defines HAVE_CHACHA and HAVE_POLY1305, there are no additional requirements for this function as of 5.7.6.  Just to be sure, can you try replacing these flags with --enable-chacha --enable-poly1305 and let me know if it helps?

If not, please confirm what version of wolfSSL you're using.  Please also try running

nm -g --defined-only

on your wolfSSL library and confirm whether you see wc_ChaCha20Poly1305_Decrypt in the output.

Thanks,
Kareem

Hi Mohammed,

As the site you are connecting to is hosted by a CDN, you will most likely need to enable SNI to connect: https://www.wolfssl.com/documentation/m … ssl_usesni
If this doesn't help you can also try enabling alt cert chains via: --enable-altcertchains

Can you share a bit about your project with wolfSSL?  Are you using wolfSSL in a personal or commercial project?  If these details are sensitive, please contact us at support [AT] wolfssl [DOT] com.

Thanks,
Kareem

Hi fenster,

To start with, build wolfSSL with --enable-distro and any other features you wish to enable, then run "make deb", this will generate an installable Debian package.  You can alternatively run "make deb-docker" to perform this build inside of a docker container.

We don't currently support building a Debian package from wolfssl-py, only a PIP package which you'll find the instructions for here: https://github.com/wolfSSL/wolfssl-py
If you'd like us to add support for this, I can help you set up a feature request, please email us at support [AT] wolfssl [DOT] com.

Thanks,
Kareem

Hi Sadanand,

Great question.  So we don't have a define called HAVE_AESCCM_8, and you don't need any extra defines.  The exact same build settings are used to enable TLS_AES_128_CCM_SHA256 and TLS_AES_128_CCM_8_SHA256.

If I'm understanding right, your connection is closing after a few seconds, is that correct?  If so, are you confident your server supports the cipher suite TLS_AES_128_CCM_8_SHA256?

Please share your user_settings.h and generate and share a full debug log.  To generate a debug log, build with --enable-debug --enable-debug-trace-errcodes and run wolfSSL_Debugging_ON() at the start of your program.

Please share some information about your project.  Are you working on a personal or commercial project?

Feel free to email us at support [AT] wolfssl [DOT] com if any of this information is sensitive.

Thanks,
Kareem

Hi Nilesh,

Great question.  So the client only needs to store/know about the root CA, to load this use wolfSSL_CTX_load_verify_buffer.  The server will load the intermediate certs and the server certs, you can use wolfSSL_CTX_use_certificate_chain_buffer for this.

During the connection, the server will send over its cert and all intermediates, then the client will verify that the chain is verified against the root CA it has loaded.

This define will go in your user_settings.h, you can find more information on and some examples of user_settings here: https://github.com/wolfSSL/wolfssl/tree … es/configs
I would recommend starting with user_settings_template.h and adjusting it to your use case.

Hi Bryce,

Thank you for your interest in wolfSSL and great question.  For Integrity OS, you will need to define __INTEGRITY or INTEGRITY, this define should be set by default by your toolchain.
We have various IDE example projects here which you may find helpful: https://github.com/wolfSSL/wolfssl/tree/master/IDE

May I ask what kind of project you are using wolfSSL in and whether it is personal or commercial?  You are welcome to email us at support [AT] wolfssl [DOT] com if these details are sensitive.

Thanks,
Kareem