Hi brunomarcoux

Please send an email to facts@wolfssl.com ands we can help you get started.

Thanks for contacting wolfSSL Support. NIST is currently selecting the next round of post-quantum crypto algorithms:
https://csrc.nist.gov/Projects/post-qua … yptography

The existing NTRU integration will not be maintained. We are aware that the NTRU library we tested with is no longer available:
https://github.com/NTRUOpenSourceProject/ntru-crypto

wolfSSL is working on support for the successor to NTRU:
https://github.com/open-quantum-safe/liboqs

You are welcome to send an email to facts@wolfssl.com to request more information.

Kind regards,
Eric @ wolfSSL Support

Hi sapi01

Need to clarify a couple points from your post:

> When I try to connect to my wolfSSL server, I'm getting `-188` on `wolfSSL_connect()`

Is this error in the client? Both peers will need the self-signed cert. You are basically doing a shared secret when doing mutual authentication and using self-signed certs.

Alternatively you could write a verify callback to override the cert failures for particular servers.

https://github.com/wolfSSL/wolfssl-exam … back.c#L55

Thanks,
Eric @ wolfSSL Support

Hello a940153,

The `SSL_VERIFY_CLIENT_ONCE` flag is regarded as unsafe and is ignored in wolfSSL. You can use session tickets to securely reconnect a peer.

Hi Tammy,

This sounds very similar to the ST HAL issue described here:
https://community.st.com/s/question/0D5 … le-missing

Thanks,
Eric @ wolfSSL Support

Hello kackle123

The web doc is out date from the code. There are two API

int MqttClient_WaitMessage_ex(MqttClient *client, MqttObject* msg,
        int timeout_ms)
{
    return MqttClient_WaitType(client, msg, MQTT_PACKET_TYPE_ANY, 0,
        timeout_ms);
}
int MqttClient_WaitMessage(MqttClient *client, int timeout_ms)
{
    if (client == NULL)
        return MQTT_CODE_ERROR_BAD_ARG;
    return MqttClient_WaitMessage_ex(client, &client->msg, timeout_ms);
}

As you can see, `MqttClient_WaitMessage` does take 2 parameters.

Are you trying to read an incoming publish, whose topic you have already subscribed? You should try setting up a publish callback. Here is an example:
https://github.com/wolfSSL/wolfMQTT/blo … ient.c#L58

Thanks,
Eric @ wolfSSL Support

Hello sahl.john

There is a fix pending for the RNG dependency. This fix will be available in the next release, although I can't provide a specific timeline. I will update as soon as the fix is available (i.e. the PR has been merged).

Thanks,
Eric @ wolfSSL Support

Hello nmehta,

In order to give you the highest priority for your FIPS question, could you please send an email to support@wolfssl.com ?

Kind regards,
Eric @wolfSSL Support

Hi Tammy,

The code changes are still making their way through the review cycle.

Hello Tammy,

I was able to reproduce the build errors with wolfSSL configured as:

./configure --enable-ssh --disable-filesystem --disable-aesgcm

I created a pull request here:
https://github.com/wolfSSL/wolfssh/pull/328

Thanks,
Eric @ wolfSSL Support

Hi cxenof03,

Welcome to the wolfSSL Forums!

The specific option for enabling TLS sessions is `HAVE_SESSION_TICKET`.

There is not currently an equivalent macro for the `./configure --enable-all` option, but you can use the "user_settings" method to get close:
https://github.com/wolfSSL/wolfssl/tree … es/configs

Here is an example that configures most of the library options:
https://github.com/wolfSSL/wolfssl/blob … ings_all.h

Thanks,
Eric @ wolfSSL Support