Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds support for channel binding for http-SSPI-Negotiate. #3509

Closed
wants to merge 2 commits into from

Conversation

georgeok
Copy link
Contributor

Attempt to add support for Secure Channel binding when negotiate authentication is used. The problem to solve is that by default IIS accepts channel binding and curl doesn't utilise them. The result was a 401 response. Scope affects only the Schannel(winssl)-SSPI combination.

@georgeok georgeok force-pushed the negotiate-sspi-https-401 branch 2 times, most recently from 189159d to 4516e49 Compare January 30, 2019 13:52
@georgeok
Copy link
Contributor Author

@MarcelRaad Since you've seen the same patch for NTLM, could you please help me out with this PR? One of the tests is failing in buildbot/curl_winssl_mingw_w64_x64_dbg. Looks like a networking issue to me. Any comments?

lib/urldata.h Outdated
@@ -980,6 +983,9 @@ struct connectdata {
void *seek_client; /* pointer to pass to the seek() above */

/*************** Request - specific items ************/
#ifdef SECPKG_ATTR_ENDPOINT_BINDINGS
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably also needs USE_WINDOWS_SSPI like in the other conditions?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback. Code updated!

@MarcelRaad
Copy link
Member

Yes, looks unrelated. The code changes look good to me too,

@MarcelRaad
Copy link
Member

Testing right now. I don't expect any problems, so if there are no objections, I'll merge this later today.

@MarcelRaad MarcelRaad self-assigned this Feb 1, 2019
@MarcelRaad MarcelRaad closed this in a730432 Feb 1, 2019
@MarcelRaad
Copy link
Member

Thank you very much!

@lock lock bot locked as resolved and limited conversation to collaborators May 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants