curl(schannel): increase renegotiation timeout to 60 seconds#192
Merged
Conversation
As reported by Tim Omta in curl/curl#21270, the renegotiation timeout of 7 seconds caused serious problems in some scenarios, and was already increased to 60 seconds in cURL's main branch, in time for their v8.20.0 release on April 29th. Unfortunately, this is too late for the patch to make it into Git for Windows v2.54.0, which is currently scheduled for April 20th (see https://gh.io/gitCal for details). So let's backport the patch. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
mjcheetham
approved these changes
Apr 13, 2026
Member
Author
|
/deploy mingw-w64-curl The i686/x86_64 and the arm64 workflow runs were started. |
This comment was marked as outdated.
This comment was marked as outdated.
Member
Author
|
/add relnote bug When fetching/pushing via Secure Channel (the default TLS/SSL method), the timeout to renegotiate (e.g. using client certificates) was recently reduced to 7 seconds, which was too short. It has been extended to 60 seconds. The workflow run was started |
github-actions bot
pushed a commit
to git-for-windows/build-extra
that referenced
this pull request
Apr 13, 2026
When fetching/pushing via Secure Channel (the default TLS/SSL method), the timeout to renegotiate (e.g. using client certificates) was recently reduced to 7 seconds, which was too short. It has been [extended to 60 seconds](git-for-windows/MINGW-packages#192). Signed-off-by: gitforwindowshelper[bot] <gitforwindowshelper-bot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As reported by Tim Omta in curl/curl#21270, the renegotiation timeout of 7 seconds caused serious problems in some scenarios, and was already increased to 60 seconds in cURL's main branch, in time for their v8.20.0 release on April 29th.
Unfortunately, this is too late for the patch to make it into Git for Windows v2.54.0, which is currently scheduled for April 20th (see https://gh.io/gitCal for details).
So let's backport the patch.