aboutsummaryrefslogtreecommitdiff
path: root/docs/LICENSE-MIXING
AgeCommit message (Collapse)Author
2016-04-06URLs: change http to https in many placesViktor Szakats
Closes #754
2016-02-03URLs: Change more haxx.se URLs from http: to https:Dan Fandrich
2016-02-02HTTPS: update a bunch of URLs from HTTP to HTTPSDaniel Stenberg
2015-06-15LICENSE-MIXING: update URLsViktor Szakats
* use SSL/TLS where available * follow permanent redirects
2015-06-15LICENSE-MIXING: refreshedDaniel Stenberg
2014-09-10LICENSE-MIXING: removed krb4 infoDaniel Stenberg
krb4 has been dropped since a while now
2014-07-16Remove all traces of FBOpenSSL SPNEGO supportDavid Woodhouse
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.
2011-01-21Mention axTLS in some more documentationDan Fandrich
2007-03-29Added a libssh2 section.Dan Fandrich
2007-02-12Rob Crittenden added support for NSS (Network Security Service) for theDaniel Stenberg
SSL/TLS layer. http://www.mozilla.org/projects/security/pki/nss/
2006-07-07yassl can be used nowDaniel Stenberg
2006-01-19corrected factual mistake about BSD license in the krb4.c codeDaniel Stenberg
2005-08-29Added GNU GSS and separate sections for MIT GSS and Heimdal and added infoDaniel Stenberg
about what each single lib may be used for.
2005-07-07mention the exception only once ;-)Daniel Stenberg
2005-04-07added some blurb about the GnuTLS licenseDaniel Stenberg
2004-09-19added URL to the exception paragraph in the GPL FAQDaniel Stenberg
2004-04-27Added LICENSE-MIXING to the release archiveDaniel Stenberg