> What does your implementation do differently, and which platforms does it
> work on?
It is still an early prototype, but it already allows dynamic expansion of the
secure heap (as well as shrinking) and I hope to add support for Microsoft
Windows after the POSIX / Linux implementation.
The intent is that you replace the upper layer, CRYPTO_secure_x
What does your implementation do differently, and which platforms does it work
on?
We would consider a patch of this nature. There are plenty of platforms where
we don’t know and don’t support secure memory. Having customisable hooks would
allow them secure memory too.
Yes, is *must* be thread safe — just like the existing implementation.
The malloc and free are the impo
