- Jul 17, 2014
-
-
Daniel Stenberg authored
-
- Jul 16, 2014
-
-
David Woodhouse authored
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.
-
- Jul 10, 2014
-
-
Steve Holme authored
-
Daniel Stenberg authored
... with a mention of *NOSIGNAL, based on talk in bug #1386
-
- Jul 05, 2014
-
-
Dan Fandrich authored
-
- Jul 03, 2014
-
-
Dimitrios Siganos authored
-
Dimitrios Siganos authored
-
Dimitrios Siganos authored
-
Dimitrios Siganos authored
-
Dimitrios Siganos authored
-
-
- Jul 02, 2014
-
-
Dan Fandrich authored
-
- Jul 01, 2014
-
-
Dan Fandrich authored
-
- Jun 28, 2014
-
-
Steve Holme authored
-
- Jun 25, 2014
-
-
Dan Fandrich authored
-
- Jun 23, 2014
-
-
Dan Fandrich authored
-
- Jun 21, 2014
-
-
Daniel Stenberg authored
mainly to improve how the web versions render
-
Dan Fandrich authored
-
Daniel Stenberg authored
... by using the "\fIopt(3)\fP" syntax they will be linked properly when the web version of the page is generated.
-
Daniel Stenberg authored
-
Daniel Stenberg authored
... to the always-copy-char *-argument. And fix some minor mistakes.
-
Daniel Stenberg authored
With all the new individual option man pages created, this now refers to each separate one instead of duplicaing the info. Also makes this page easier to overview.
-
Dan Fandrich authored
-
- Jun 20, 2014
-
-
Daniel Stenberg authored
shorten descriptions, mostly refer to the separate descriptions
-
Daniel Stenberg authored
-
Dan Fandrich authored
-
Dan Fandrich authored
-
- Jun 19, 2014
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
... and fixed mancheck to ignore obsolete options
-
Daniel Stenberg authored
Now all current options have their own man pages.
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
To be further discussed, debated and edited
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Jun 18, 2014
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Dan Fandrich authored
-