fixed warning with gcc 4.x (hopefully); dynamincally imported UseAccurateCaseForPaths() for CLIB port to be stonetime-compatible (NW 3.x).

countermeasures code path.

Improve "universal" alignment type in struct memdebug

undef standard *printf before (re)defining them

based on his comments/suggestions.

fixed link order in case libssh2 is build with zlib.

non-ASCII systems.

it into a few new functions.
Fixed a few leaks in out of memory conditions, including for test case 231.

LIBSSH2_APINO

changed 'rm -f' to 'del /f' so it works without GnuUtils as Peteris Krumins pointed out; changed to use latest external libs.

release the next curl until there is a libssh2 0.16 released.

(http://curl.haxx.se/bug/view.cgi?id=1766320) pointing out that the libcurl
code accessed two curl_easy_setopt() options (CURLOPT_DNS_CACHE_TIMEOUT and
CURLOPT_DNS_USE_GLOBAL_CACHE) as ints even though they're documented to be
passed in as longs, and that makes a difference on 64 bit architectures.

after 7.16.2. This is much due to the different treatment file:// gets
internally, but now I added test 231 to make it less likely to happen again
without us noticing!

was set, this should make it work for all cases!

passed to it with curl_easy_setopt()! Previously it has always just refered
to the data, forcing the user to keep the data around until libcurl is done
with it. That is now history and libcurl will instead clone the given
strings and keep private copies.

NTLM, and he provided test code and a test server and we worked out a bug
fix. We failed to count sent body data at times, which then caused internal
confusions when libcurl tried to send the rest of the data in order to
maintain the same connection alive.

(and then I did some minor reformatting of code in lib/http.c)

of a socket after it has been closed, when the FTP-SSL data connection is taken
down.

support for the OS/400 Secure Sockets Layer library

some few internal identifiers to avoid conflicts, which could be useful on
other platforms.

(http://curl.haxx.se/bug/view.cgi?id=1757328) and submitted a patch. It turns
out we broke login to FTP servers that don't require (nor understand) PASS
after the USER command