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).
Yeps.
> 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.
-- / daniel.haxx.se _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-develReceived on 2011-09-28