In the FAQ here: https://www.wolfssl.com/docs/frequently … wolfCrypt?melon playground
It says:
"You can configure wolfSSL with --enable-staticmemory or by defining the WOLFSSL_STATIC_MEMORY macro. However, this feature is limited to basic TLS connections and currently is not supported in wolfCrypt."And I've seen elsewhere that wolfCrypt is needed for wolfHSM.
Can I get confirmation that if I want to use static memory allocation with wolfSSL that I will not be able to use either wolfCrypt or wolfHSM?
Also, do I need wolfHSM in order to run wolfSSL on an HSM? Or is it just helpful?
Great question! From the FAQ, it seems static memory isn’t currently supported in wolfCrypt, which affects wolfHSM. wolfHSM isn't strictly required but adds useful integration features.