mirror of
https://github.com/curl/curl.git
synced 2024-11-27 05:50:21 +08:00
9ad282b1ae
This is just fundamentally broken. SPNEGO (RFC4178) is a protocol which allows client and server to negotiate the underlying mechanism which will actually be used to authenticate. This is *often* Kerberos, and can also be NTLM and other things. And to complicate matters, there are various different OIDs which can be used to specify the Kerberos mechanism too. A SPNEGO exchange will identify *which* GSSAPI mechanism is being used, and will exchange GSSAPI tokens which are appropriate for that mechanism. But this SPNEGO implementation just strips the incoming SPNEGO packet and extracts the token, if any. And completely discards the information about *which* mechanism is being used. Then we *assume* it was Kerberos, and feed the token into gss_init_sec_context() with the default mechanism (GSS_S_NO_OID for the mech_type argument). Furthermore... broken as this code is, it was never even *used* for input tokens anyway, because higher layers of curl would just bail out if the server actually said anything *back* to us in the negotiation. We assume that we send a single token to the server, and it accepts it. If the server wants to continue the exchange (as is required for NTLM and for SPNEGO to do anything useful), then curl was broken anyway. So the only bit which actually did anything was the bit in Curl_output_negotiate(), which always generates an *initial* SPNEGO token saying "Hey, I support only the Kerberos mechanism and this is its token". You could have done that by manually just prefixing the Kerberos token with the appropriate bytes, if you weren't going to do any proper SPNEGO handling. There's no need for the FBOpenSSL library at all. The sane way to do SPNEGO is just to *ask* the GSSAPI library to do SPNEGO. That's what the 'mech_type' argument to gss_init_sec_context() is for. And then it should all Just Work™. That 'sane way' will be added in a subsequent patch, as will bug fixes for our failure to handle any exchange other than a single outbound token to the server which results in immediate success. |
||
|---|---|---|
| .. | ||
| examples | ||
| libcurl | ||
| .gitignore | ||
| BINDINGS | ||
| BUGS | ||
| CONTRIBUTE | ||
| curl-config.1 | ||
| curl.1 | ||
| DISTRO-DILEMMA | ||
| FAQ | ||
| FEATURES | ||
| HISTORY | ||
| HTTP-COOKIES | ||
| index.html | ||
| INSTALL | ||
| INSTALL.cmake | ||
| INSTALL.devcpp | ||
| INTERNALS | ||
| KNOWN_BUGS | ||
| LIBCURL-STRUCTS | ||
| LICENSE-MIXING | ||
| MAIL-ETIQUETTE | ||
| Makefile.am | ||
| MANUAL | ||
| mk-ca-bundle.1 | ||
| README.cmake | ||
| README.netware | ||
| README.win32 | ||
| RELEASE-PROCEDURE | ||
| RESOURCES | ||
| ROADMAP.md | ||
| SECURITY | ||
| SSL-PROBLEMS | ||
| 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.