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
Hi All,
small question - I was playing around with the CMS interface and I was
wondering what is the right way to generate a signed and encrypted CMS.
In particular, for PKCS#7, you could use the signed_and_encrypted
choice... but in CMS, there is the envelopedData ... but that does not
allow
Does anyone have a straightforward example of the canonical way to
handle SSL_shutdown() in OpenSSL 1.1.1? I mean both when my code is
the initiator of the shutdown and also when I'm the peer, and also for
both blocking and non-blocking BIOs?
I've read and re-read the SSL_shutdown() man page and
Hello,
I have been experimenting with a custom secure heap implementation recently.
Would OpenSSL be open to a patch that allows users to replace the OpenSSL
implementation with their own, similarly to how CRYPTO_set_mem_functions works?
Based on mem_sec.c, at least sh_malloc, sh_free, sh_actua
