If an empty string is passed to CURLOPT_SSH_PUBLIC_KEYFILE, libcurl will pass no public key to libssh2 which then tries to compute it from the private key. This is known to work when libssh2 1.4.0+ is linked against OpenSSL. |
||
|---|---|---|
| .. | ||
| examples | ||
| libcurl | ||
| .gitignore | ||
| BINDINGS | ||
| BUGS | ||
| CONTRIBUTE | ||
| curl-config.1 | ||
| curl.1 | ||
| DISTRO-DILEMMA | ||
| FAQ | ||
| FEATURES | ||
| HISTORY | ||
| index.html | ||
| INSTALL | ||
| INSTALL.cmake | ||
| INSTALL.devcpp | ||
| INTERNALS | ||
| KNOWN_BUGS | ||
| LICENSE-MIXING | ||
| MAIL-ETIQUETTE | ||
| Makefile.am | ||
| MANUAL | ||
| README.cmake | ||
| README.netware | ||
| README.win32 | ||
| RESOURCES | ||
| SSLCERTS | ||
| THANKS | ||
| TheArtOfHttpScripting | ||
| TODO | ||
| VERSIONS | ||
_ _ ____ _
___| | | | _ \| |
/ __| | | | |_) | |
| (__| |_| | _ <| |___
\___|\___/|_| \_\_____|
README.win32
Read the README file first.
Curl has been compiled, built and run on all sorts of Windows and win32
systems. While not being the main develop target, a fair share of curl users
are win32-based.
The unix-style man pages are tricky to read on windows, so therefore are all
those pages converted to HTML as well as pdf, and included in the release
archives.
The main curl.1 man page is also "built-in" in the command line tool. Use a
command line similar to this in order to extract a separate text file:
curl -M >manual.txt
Read the INSTALL file for instructions how to compile curl self.