Hi Alex,

What platform and OS are you using?  How much stack/heap are you giving to wolfSSL?
What kind of webpage are you serving with wolfSSL?  Is it something that would spawn multiple connections?
Does closing your Chrome tab and opening a new one resolve the issue, or does it require a full browser restart?

If this information is too sensitive to share in a public forum, feel free to contact us at support@wolfssl.com

Thanks,
Kareem

Hi Alex,

A couple of questions:
1) Does a hard refresh (usually Ctrl+F5) show the same issue in your browser?
2) What version of wolfSSL are you using?  Do you still see the issue with the latest wolfSSL, 5.0?

Thanks,
Kareem

We recently released 5.0 which fixes various bugs in 4.8.1, please try updating and let me know if you still see any issues.

Hello rahmanikivi724,

Your platform does have a hardware RNG, you can see the details here: https://www.st.com/en/microcontrollers- … 446re.html
So you should undefine NO_STM32_RNG so we use our STM32 hardware RNG support, which will include a wc_GenerateSeed implementation.  You should also undefine WOLFSSL_GENSEED_FORTEST.

Thanks,
Kareem

You should have stm32f4xx_hal.h, it needs to be generated by STM32CubeIde.  You may be running into a path issue, make sure your include paths include stm32f4xx_hal.h.
You need to add your platform to the user_settings.h template, see our documentation: https://github.com/wolfSSL/wolfssl/tree … /STM32Cube and user_settings.h template under "#warning Please define a hardware platform!".  You should define NO_STM32_HASH/CRYPTO if applicable for your platform.  You do not need WOLFSSL_STM32F427_RNG defined.
Also see our video here: https://www.youtube.com/watch?v=pUd2HEfBp3w
For debugging, you need to build with DEBUG_WOLFSSL and you need to call wolfSSL_Debugging_ON() before any other code.

Hi rahmanikivi724,

A couple of things to try.
First, you should always call wolfSSL_Init() before any other wolfSSL functions.
Second, try defining WOLFSSL_STM32F427_RNG to use our STM32F4xx codepath for your RNG.

If this doesn't help, please enable debugging by building with DEBUG_WOLFSSL and running wolfSSL_Debugging_ON() before your code, and attach debug logs.  The return code of wc_InitRng would also be helpful.

Thanks,
Kareem

Hi stillwater,

We do not currently support custom handshake extensions.  I can enter a feature request for you, but there's no guarantee of when it will be implemented.
Alternatively, you can contact us at facts@wolfssl.com to discuss code consulting for this feature.

Thanks,
Kareem

Hi rlev,

Yes, when using the MqttClient_Subscribe API to subscribe, you can pass as many topics as you'd like in the array MqttSubscribe->topics as long as you set topic_count correctly.
Here are a couple of examples that subscribe to a single topic, to expand them you'd just iterate over each topic and set their parameters accordingly:
https://github.com/wolfSSL/wolfMQTT/blo … ent.c#L383
https://github.com/wolfSSL/wolfMQTT/blo … ple.c#L399

Thanks,
Kareem

Hi rr9mvp,

While we have not ported wolfSSH/SFTP to FreeRTOS without POSIX, we have ported wolfSSH/SFTP to various platforms which you can find here:
https://github.com/wolfSSL/wolfssh/blob … ssh/port.h
https://github.com/wolfSSL/wolfssh/blob … src/port.c

If you are interested in having us help you port to your platform, please contact us at facts@wolfssl.com

Thanks,
Kareem

Hello Gary,

Do you see this issue with curl for all sites, or just microsoft.com?
Can you try the WOLFSSL_ALLOW_NO_CN_IN_SAN flag?
If that doesn't help, please generate a debug log by rebuilding with WOLFSSL_DEBUG defined and attach it here.  Please also include your curl command line or code.

For wolfSSL's client, try using -A to pass in your CA cert, not -a.

Thanks,
Kareem

Hi Noufal,

See here for examples and documentation on building wolfSSL with Yocto: https://github.com/wolfSSL/meta-wolfssl

Thanks,
Kareem

Hello ENOTTY,

I was able to reproduce your issue on that commit.  Looks like we've just checked in a fix here:
https://github.com/wolfSSL/wolfssl/comm … 8a742dde57
I retested with this commit applied and everything is building for me now.  Let me know if it works for you.

Thanks,
Kareem