cURL / Mailing Lists / curl-library / Single Mail


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

From: Steve Holme <>
Date: Mon, 14 Jul 2014 20:15:40 +0100

On Mon, 14 Jul 2014, Michael Osipov wrote:

> > 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.

Sorry - I can be a little dippy at times :(

> 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.

I would be interested to know what aspects of SASL you were referring to and any other thoughts/suggestions you have on the topic.

Kind Regards


List admin:
Received on 2014-07-14