On Tue, 1 Apr 2014, Ophir Orly wrote:
1. The cause for the gssapi compilation issues is that the curl configure script uses krb5-config to get the compilation flags, and apparently we have that misconfigured. I would have thought that the it will take the --prefix lib instead of using the tools, but I guess there's a reason for this behavior.
Yes, because krb5-config is usually the better choice since it has info from the installation of the krb5 lib(s) and lets us avoid "guessing" in the configure script.
I thought it might be relevant since I've read something about NTLMSSP being removed from Windows Vista and Windows Server 2008 in favor of the Kerberos protocol. Will that cause issues with current NTLMv2 implementation?
No. libcurl does NTLM either completely by itself (using a crypto backend) or it hands if off to Windows SSPI, but none of that requires or uses any krb things as far as I can tell.
-- / daniel.haxx.se ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
