mirror of
https://github.com/moparisthebest/curl
synced 2024-11-10 11:35:07 -05:00
3cffcba3d0
On second thought, I think CURLE_TLSAUTH_FAILED should be eliminated. It was only being raised when an internal error occurred while allocating or setting the GnuTLS SRP client credentials struct. For TLS authentication failures, the general CURLE_SSL_CONNECT_ERROR seems appropriate; its error string already includes "passwords" as a possible cause. Having a separate TLS auth error code might also cause people to think that a TLS auth failure means the wrong username or password was entered, when it could also be a sign of a man-in-the-middle attack. |
||
|---|---|---|
| .. | ||
| 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 | ||
| 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.