-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
adding http.schannel.checkRevoke support #1450
adding http.schannel.checkRevoke support #1450
Conversation
http.c
Outdated
@@ -753,6 +753,12 @@ static CURL *get_curl_handle(void) | |||
} | |||
#endif | |||
|
|||
#if LIBCURL_VERSION_NUM >= 0x074400 | |||
if (!strcmp("schannel", http_ssl_backend) && http_schannel_check_revoke) { |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Looks good so far, I offered a couple of suggestions. I also would prefer to have these patches squashed into a single one, and some documentation added to As to tests, I do not really know that we can test for this. We have to rely on cURL's own testing, I would imagine. As it is, the implementation on the Git side is straight-forward enough that I cannot see any bug. So essentially I would suggest to:
|
@dscho thanks for the feedback. I'll bump this when it's ready to go around again. |
This adds support for a new http.schannel.checkRevoke config value. This config value is only used if http.sslBackend is set to "schannel", which forces cURL to use the Windows Certificate Store when validating server certificates associated with a remote server. This config value should only be set to "false" if you are in an environment where revocation checks are blocked by the network, with no alternative options. This is only supported in cURL 7.44 or later. Signed-off-by: Brendan Forster <github@brendanforster.com>
🍎 |
Sorry for the delay! I somehow missed that this was ready for merging. For the record: I plan on releasing Git for Windows v2.16.1(2) tomorrow, thanks to a couple of component updates that address CVEs (nothing that I think is exploitable, but let's be safe). |
All good. I thought you were taking a well-deserved break 😛 |
Heh... Nope, I was sick most of last week, but had to work nevertheless (too much important stuff required from me). |
When using Secure Channel as HTTPS transport behind a proxy, it may be necessary to disable revocation checks, [which is now possible](git-for-windows/git#1450). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
adding http.schannel.checkRevoke support
adding http.schannel.checkRevoke support
adding http.schannel.checkRevoke support
adding http.schannel.checkRevoke support
adding http.schannel.checkRevoke support
…ke-support adding http.schannel.checkRevoke support
…ke-support adding http.schannel.checkRevoke support
Fixes #1446
Opening this up early to gather feedback (I'm not strong on curl's internals) as I think we're all in agreement on the approach:
schannel
is the backend