This is my version:
curl 7.34.0-20131113 (x86_64-unknown-linux-gnu) libcurl/7.34.0-20131113 OpenSSL/1.0.0 zlib/1.2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: GSS-Negotiate IPv6 Largefile NTLM NTLM_WB SSL libz

---
** [bugs:#1302] HTTP Auth Negotiate sends Kerberos token instead of SPNEGO token**
**Status:** open
**Created:** Wed Nov 13, 2013 12:07 PM UTC by Michael Osipov
**Last Updated:** Wed Nov 13, 2013 12:07 PM UTC
**Owner:** nobody
When a server challenges a client with 'WWW-Authenticate: Negotiate', it expects a SPNEGO token. Unfortunately, curl needs to be compiled with fbopenssl for this. If you compile with GSS-API only it generates a Kerberos 5 token in lib/curl_gssapi.c line 64, NO_OID. This makes the implemenation select a default mech (namely KRB 5).
For HTTP this can be easily patched with something like this: http://code.google.com/p/serf/issues/attachmentText?id=89&aid=890000000&name=serf-spnego.patch&token=_HwqdhFej2jHi5_6V0XTh311VPM%3A1351042419228
My locally patched version works as desired. The function Curl_gss_init_sec_context is used in several spots, so if someone really needs Kerberos instead of SPNEGO another argument for passing the OID is necessary (FTP, SOCKS). With that change, fbopenssl is redundant and can be completely removed.
If not a wrapped SPNEGO token is send, an acceptor can react with:
GSSException: No credential found for: 1.2.840.113554.1.2.2 usage: Accept
        at sun.security.jgss.GSSCredentialImpl.getElement(GSSCredentialImpl.java:577)
        at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:317)
        at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:285)
I have reported the very same issue with Subversion and libserf: http://code.google.com/p/serf/issues/detail?id=89
The SSPI version does not suffer from this because "Negotiate" is passed to AcquireCredentialsHandle.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.