cURL / Mailing Lists / curl-library / Single Mail


Re: [PATCH] SF bug #1302: HTTP Auth Negotiate sends Kerberos token instead of SPNEGO token

From: Michael Osipov <>
Date: Mon, 14 Jul 2014 10:01:45 +0200

Am 2014-07-13 20:36, schrieb Steve Holme:
> On Sun, 13 Jul 2014, Michael Osipov wrote:
>>> On a side note, we are currently missing support for the GSSAPI
>>> mechanism and Winbind NTLM implementation in the email
>>> protocols.
>> Are you implementing SASL your self for curl or do you use
>> CyrusSASL? I know that Windows has a native SASL impl but that
>> seems to be available on Windows Server only.
> We currently have native support for the following SASL authentication mechanisms:
> CRAM-MD5, DIGEST-MD5, LOGIN, NTLM and PLAIN with support for extensions such as OAUTH2.
> This could be extended to include the HTTP authentication mechanisms as well and turn our SASL module into a more generic authentication layer that includes both SASL and HTTP mechanisms.
> I don't know enough about CyrusSASL at the moment but that was one of the third-party libraries I was thinking of that we could integrate with - if we wanted to.


you obviously misunderstood me. I was talking about the SASL
implementation itself not the mechanisms it supports. That's why I
referred to Cyrus SASL. There are, of course, other implementations like
GNU SASL, Heimdal, etc.


List admin:
Received on 2014-07-14