Hello Scotty2541,

Sounds like there could be a missing check for TI_RTOS. Would you please let us know if this fixes the build issue?

diff --git a/src/ssl.c b/src/ssl.c
index 7432ffe73..486b3129a 100644
--- a/src/ssl.c
+++ b/src/ssl.c
@@ -31736,7 +31736,7 @@ int wolfSSL_RAND_write_file(const char* fname)
     return bytes;
 }
 
-#ifndef FREERTOS_TCP
+#if !defined(FREERTOS_TCP) && !defined(WOLFSSL_TIRTOS)
 
 /* These constant values are protocol values made by egd */
 #if defined(USE_WOLFSSL_IO) && !defined(USE_WINDOWS_API)

Kind regards,
Eric @ wolfSSL Support

I just pushed another commit that fixes the build errors for

--disable-ecc

.

Thanks,
Eric

Hello iain.moir

Welcome to the wolfSSL Support Forums!

We are constantly striving to make the build process as painless as possible, but there will always be some unique environments that need a little extra effort. We are very adept at helping users to get started with the library.

Here is our QuickStart guide:
https://www.wolfssl.com/docs/quickstart/

Please email us at support@wolssl.com with any questions.

Thanks,
Eric @ wolfSSL Support

Hi Hu,

Welcome to the wolfSSL Support Forums!

The RIOT-OS build does not use the same instructions as the linux build for wolfSSL. Configuration changes should be made in the user_settings.h header. You should add a define for `WOLFSSL_AES_COUNTER`.

https://github.com/RIOT-OS/RIOT/blob/ma … settings.h

Thanks,
Eric @ wolfSSL Support

Hello steins,

Thanks for joining the wolfSSL Support forums. You are trying to isolate all the functions for parsing and decoding a certificate? Any particular reason? The compiler tools should allow you to optimize any unused functionality.

What is the environment you are building in / for?

Thank,
Eric @ wolfSSL Support

Hi Gus,

Thanks for the update. Next step in debugging this would be to review a pcap of the failing handshake.

If you'd prefer to move off this public forum, please send an email to support@wolfssl.com referencing this forum thread and attach a pcap of the handshake.

Thanks,
Eric @ wolfSSL Support

Hi Remy,

No, I do not think you need the pk callback option, but you mentioned earlier in the thread.

The `NO_ECC_KEY_EXPORT` define comes from here (because `HAVE_ECC` is defined):
https://github.com/wolfSSL/wolfssl/blob … gs.h#L1821

The public key is exported to the `ssl->hsKey` structure in order to compute the shared secret.

                    ret = EccSharedSecret(ssl,
                        (ecc_key*)ssl->hsKey, ssl->peerEccKey,
                        args->output + OPAQUE8_LEN, &args->length,
                        ssl->arrays->preMasterSecret + OPAQUE16_LEN,
                        &ssl->arrays->preMasterSz,
                        WOLFSSL_CLIENT_END
                    );

Hi Tom,

Thanks for contacting wolfSSL Support. Did you already follow the guide here?
https://github.com/wolfSSL/wolfssl/tree … /XilinxSDK

It should be fairly straight forward. You would want to compile and link with the IDE. Linking with code compiled for x86 would not work.

Let us know if there are issues.

Thanks,
Eric @ wolfSSL Support

Edit: Another of our engineers has a Xilinx project repo that you might find helpful:
https://github.com/dgarske/UltraZed-EG-wolf

Hello bob190

Thanks for reaching out to wolfSSL Support.

We have lots of examples! Here is a cert manager example that should be helpful:
https://github.com/wolfSSL/wolfssl-exam … ertmanager

Please feel free top ask more questions!

Kind regards,
Eric @ wolfSSL Support

The `-K` option is expecting a path to a file.

Hello rydj

Thanks for your interest in wolfSSL. It sounds like you'll want to redirect the IO using a callback. We have an excellent examples here:
https://github.com/wolfSSL/wolfssl-exam … -callbacks

We also have a wolfSSL stunnel example in a private repository. You can request access by contacting support@wolfssl.com

Thanks,
Eric @ wolfSSL Support