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
libcurl+schannel reports different error code across versions for verify peer/host options #6003
Comments
I can't find any obvious error like this when reading the lib/vtls/schannel.c code. What does a VERBOSE log show? What does ERRORBUFFER contain after How can we reproduce this issue? |
I compiled 7.56.1 and 7.72.0 versions of curl, kept everything same in my project and rebuilt two separate applications for respective versions. Here are the logs -
|
I think you won't need logs for linux systems since this problem seems to be windows specific but here is what error buffer contains in linux -
|
I believe it came with this commit: 5a3efb1 shipped in 7.62.0. I think we can/should bring back the |
I did this
I have a server with custom ssl certificate that can be connected with curl by passing 0 to both methods below, but the problem arises when the following code is used -
This used to give error code 60 in 7.56 and I've tested in 67,71 and now 72 versions, all of which have changed this to give error 35. 35 -
CURLE_SSL_CONNECT_ERROR
and 60 -CURLE_PEER_FAILED_VERIFICATION
. The error 60 was preferred because it is more clear and unique to this situation while error 35 also results sometimes when there is a firewall or proxy breaking connections in between.Keeping my code exactly similar and the process I build is same, just changing between 7.56 and 7.72 results in two different error codes. Meanwhile all versions under linux and osx continue to work fine and give error code 60.
curl/libcurl version
It was fine till 7.56 and I'm not sure which version bug started with but the earliest I know is 7.67
[curl -V output]
I hope this is asking about the built version(the one I use libcurl libraries with)
operating system
Windows 10 Pro (version 2004)
The text was updated successfully, but these errors were encountered: