Re: Using OPENSSL_secure_malloc in a library?

Hi Sasha,

Yes, being able to create one's own heap would be a good solution for that.

Regards

Antoine.


Le 04/04/2025 à 09:01, Alexandr Nedvedicky a écrit :
> Hello Antoine,
> 
> On Thu, Apr 03, 2025 at 03:21:26AM -0700, Antoine Pitrou wrote:
> </snip>
>>
>>     Are there any guidelines to reliably use OPENSSL_secure_malloc() in a
>>     library?
>>
> 
>      I'm not aware of any guidelines on how to use OPENSSL_secure_malloc() in
>      library. I took a look at the source code and indeed the secure memory
>      is global. Your question feels like feature request to allow other
>      components/libraries create their own secure memory instances.
>      Either by introducing a new CRYPTP_secure__malloc_init() variant which
>      will return a handle/pointer to secure heap or adding secure heap to
>      library context. I think both those approaches would be safe for your
>      usecase.
> 
> thanks and
> regards
> sashan
> 

-- 
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/457b5146-ab6d-4394-a270-117e40de4fc7%40python.org.