Subject: Re: Patch to ticket 228

Re: Patch to ticket 228

From: Daniel Stenberg <>
Date: Wed, 28 Sep 2011 23:45:02 +0200 (CEST)

On Sun, 25 Sep 2011, Jernej Kovacic wrote:

> The function's parameters will be a session pointer, method_type and (as an
> output parameter) a pointer to array of strings.

Sounds fine to me!

> If the function fails it will free the allocated memory (if necessary)
> itself. If the function succeeds and returns a valid list, the user must
> free it when he doesn't need it anymore. This is done by calling
> libssh2_free (which actually calls LIBSSH2_FREE).


> The possible problem is with thread safety as in general malloc cannot be
> considered as thread safe (it depends on the C-library, compiler settings
> etc.)

If thread-safety with malloc is a problem, then every malloc libssh2 done has
that problem and then the application would've already replaced the default
one with a replacement that works better!

> And finally let me ask one (not so much) offtopic question. Except at AES,
> CTR mode is not supported among symmetric algorithms. Is the reason for this
> in OpenSSL or something else?

I'm not aware of any particular reason.

Received on 2011-09-28