aboutsummaryrefslogtreecommitdiff
path: root/install-sh
AgeCommit message (Collapse)Author
2015-04-30configure: remove autogenerated files by autoconfMichael Osipov
* install-sh is always regenerated * mkinstalldirs was already redudant years ago. Automake uses install for that. See: http://lists.gnu.org/archive/html/automake/2007-03/msg00015.html
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.
2013-02-13install-sh: updated to support multiple source files as argumentsDaniel Stenberg
Version 7.29.0 uses Makefiles generated with a newer version of the autotools than the previous 7.28.1. These Makefiles try to install e.g. header files by calling install-sh with multiple source files as arguments. The bundled install-sh is to old and does not support this. The problem only occurs, if install-sh is actually being used, ie. the platform install executable is to old or not usable. Example: Solaris 10. The files install-sh and mkinstalldirs are now updated with the automake 1.11.3 versions. A better fix might be to completely remove them from git and force the files to be added/created during buildconf. Bug: http://curl.haxx.se/bug/view.cgi?id=1195 Reported by: Rainer Jung
2010-02-14removed trailing whitespaceYang Tse
1999-12-29Initial revisionDaniel Stenberg