cURL / Mailing Lists / curl-library / Single Mail


Re: Windows SSPI Schannel implementation ready

From: Marc Hoersken <>
Date: Mon, 11 Jun 2012 23:12:15 +0200

Hi Daniel,

2012/6/11 Daniel Stenberg <>:
> On Mon, 11 Jun 2012, Steve Holme wrote:
>> We had discussed that SSPI was a library / provider of security features
>> such a Security Contexts (GSS-Nego, NTLM, etc...) and now SSL and as such
>> should not appear on the features list in the same way that OpenSSL or
>> GNUTLS don't.
> I agree with this, generally. However in this case...
>> Do we need to keep this in for API compatibility? NTLM, GSS-Negotiate and
>> SSL tell the developer the features that the Windows SSPI library provides.
> Yes. We need to make existing libcurl-using source code keep compilign so we
> need the define to remain in the header file. We also probably need to
> provide the bit in the struct so that the ABI remain the same for existing
> code.
> We added SSPI in the curl output and as a feature bit once upon the time
> partly because libcurl built with SSPI provides certain features that
> libcurl without SSPI doesn't possess (I'm thinking of the ability to
> magically use the logged in user's username + password) so a user might in
> fact want to figure out if that ability exists or not.
> I hope none of you mind very much that I intend to bring it back again?

No problem for me. I think the best approach would be to bring it back
to keep the ABI compatiblity while still having the new version
information output.

Do you have anything else you want to discuss before merging the
Schannel branch, Daniel? :-)

Best regards,
List admin:
Received on 2012-06-11