Someone correct me if I'm wrong, but I'm afraid it's not likely that
openssl will work for your use case. You might try wolfSSL, polarSSL, or
some purpose-built embedded encryption librarly. If you have a specific
cryptographic operation to achieve, it might help point you in the right
direction.
> Ping !!!
You didn't get a reply in 24 hours from an open source mailing list? A little
patience.
> Upon code-browsing, I am beginning to feel that OpenSSL uses program-buffer,
> which is used for malloc/free.
OpenSSL uses malloc, etc. Look at crypto/mem.c and (in 1.1.0 and master) the
Ping !!!
Upon code-browsing, I am beginning to feel that OpenSSL uses
program-buffer, which is used for malloc/free.
Am I right?
If yes, is there a place where the maximum-size of "in-program-buffer-heap"
is defined?
On Tue, Nov 22, 2016 at 7:33 PM, Ajay Garg wrote:
>
Hi All.
I wish to compile openssl libraries for a STM32-processor (which would then
be linked statically with our application-framework code).
Now. I believe that OpenSSL uses tonnes of "malloc"s and "free"s. But for
bare-metal-systems (without any formal OSes), we generally don't have any