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

Hi stroebeljc

Thanks for your note. The most up to date documentation is the Doxygen created files in the repository. We are discussing a plan for  our other docs moving forward.

Thanks,
Eric @ wolfSSL Support

Hello stroebeljc

You would need to load the same cert on both peers. Else you could setup a verify callback that overrides the error.

Here is an example:
https://github.com/wolfSSL/wolfssl-exam … callback.c

Hi Arun,

Thanks for contacting wolfSSL Support. Adding support for SRP ciphers sounds great!

Here is a description of the steps for adding a custom cipher:
https://www.wolfssl.com/adding-alternat … library-2/

If you are interested in contributing your changes, you can open a pull request at https://github.com/wolfSSL/wolfssl.

Kind regards,
Eric @ wolfSSL Support

Hello @marlanagakalyan

Thanks for your interest in wolfMQTT. We do not currently have a Keil example for the wolfMQTT library, but you could certainly extrapolate from the existing wolfSSL examples:
https://github.com/wolfSSL/wolfssl/tree … RM/wolfSSL

I am adding your request to features queue.

Requested Feature: wolfMQTT with Keil example
Source Link: https://www.wolfssl.com/forums/topic1678-wolfmqtt.html
Requested Date: 02 FEB 2021
Implementation Date: Unfunded effort, no timeline

We try to work on requested features whenever we get free engineering cycles unless a customer decides to back the effort for a finite implementation timeline. If at any time a feature becomes a progress blocker for a project it can be accelerated by contacting the an account business manager.

Could you tell us a bit more about your project? Feel free to email us at support@wolfssl.com if you'd prefer to keep details off the forum.

What is your operating environment?