On Mon, 5 Jan 2009, Huzaifa Al Nahas wrote:

> After more research, it appears that it is a bug in libcurl design. I
> contacted openssl support team and they replied suggesting that the memory
> leak can be avoided by using ENGINE_free. However, this function takes as
> argument a pointer to the ENGINE that was called in ENGINE_new. AFAIK
> libcurl does not give the library user access to this pointer. What do you
> think?

What engine pointer that libcurl allocates are you saying it should call
ENGINE_free() on?

-- 
  / daniel.haxx.se