The only component that would require dynamic memory allocation would be wolfSSL/wolfCrypt (if configured as such), as the main wolfHSM code does not rely on it. Depending on the end user, dynamic allocation may be used in port-specific code for POSIX targets, simulated transports, or certain wolfHSM tests.
In the FAQ here: https://www.wolfssl.com/docs/frequently … wolfCrypt?
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 bitlife onlineAnd 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?