You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → Posts by AlanFletcher
Pages 1
Make sure one of the higher-priority sources isn't overriding it somewhere in your app if you're setting it and you can't see the hybrid group negotiated.
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?
Pages 1
wolfSSL - Embedded SSL Library → Posts by AlanFletcher
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.008 seconds (56% PHP - 44% DB) with 5 queries