Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
http: add support for selecting SSL backends at runtime
The Pull Request at curl/curl#1601 adds support for choosing the SSL backend at runtime to cURL, and will hopefully be merged before version 7.56.0 comes out. Git for Windows will ship with those patches backported to 7.54.1 (and come August 9th, 2017, 7.55.0 and later). This patch adds the Git side of that feature: by setting http.sslBackend to "openssl" or "schannel", Git for Windows can now choose the SSL backend at runtime. This comes in handy because Secure Channel ("schannel") is the native Windows solution, accessing the Windows Credential Store, thereby allowing for enterprise-wide management of certificates. For historical reasons, Git for Windows needs to support OpenSSL still, as it has previously been the only supported SSL backend in Git for Windows for almost a decade. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
- Loading branch information
d81216e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if that's appropriate to comment at such place, but I've found out that a large amount of people are having trouble with this question here:
fatal: Could not set SSL backend to 'schannel': already set
To solve this issue, simply run
git config --global --unset http.sslBackend
in your Git Bash.Administrators: If you found out that this comment is inappropriate, please E-Mail me or contact me with any method you would like, and I will remove this comment as soon as I got the message that says this comment should not be here. Sorry first for the mis-use of commit comment.
d81216e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, commit comments are only noted by the original authors. So a much better idea would be to report this as a bug at https://github.com/git-for-windows/git/issues/new, or via the Git mailing list or the Git for Windows mailing list.
That suggests that a large amount of people do not upgrade their Git for Windows version.
No need to delete it. (And I can't E-Mail you, as I do not have your email address.)