-
Notifications
You must be signed in to change notification settings - Fork 612
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
Don't set http.sslCAInfo for schannel #172
Don't set http.sslCAInfo for schannel #172
Conversation
f81b5e4
to
d015e35
Compare
I always try ;-) Thank you for your contribution!
If you don't mind, I would prefer a different approach:
What do you think? |
(Oh, and if you agree, and do it that way, simply force-push to the same branch; This will update the PR automatically.) |
Yes, I'm willing to follow your suggestion. Then nasty details come to the surface: I'd like to reorder sslCAInfo and sslBackend, but sslCAInfo is inside |
Personally, I would prefer the block {
Configure http.sslBackend according to the user's choice.
}
if RdbCurlVariant[GC_WinSSL].Checked then begin
Cmd:='schannel';
end else begin
Cmd:='openssl';
end;
if not Exec(AppDir+'\{#MINGW_BITNESS}\bin\git.exe','config --system http.sslBackend '+Cmd,
AppDir,SW_HIDE,ewWaitUntilTerminated,i) then
LogError('Unable to configure the HTTPS backend: '+Cmd);
if HttpDummySet then begin
if not Exec(AppDir+'\{#MINGW_BITNESS}\bin\git.exe','config --system --unset http.dummy',
AppDir,SW_HIDE,ewWaitUntilTerminated,i) then
LogError('Unable to unset http.dummy');
end; to be moved just before the line What do you think? |
Preparation for next commit which will unset variable in this section. Without re-ordering we would trigger git config issue (empty section left). Signed-off-by: Aleksander Salwa <asalwa@ra.rockwell.com>
d015e35
to
11473c2
Compare
I've updated and pushed my branch according to your suggestions. |
This way native Windows mechanism of certificates distribution will be used. This addresses #1409. Signed-off-by: Aleksander Salwa <asalwa@ra.rockwell.com>
11473c2
to
3bd10bf
Compare
Very nice! Thank you! |
When configuring HTTPS transport to use Secure Channel, [we now refrain from configuring `http.sslCAInfo`](#172). This also helps Git LFS (which uses Git for Windows' private `http.sslCAInfo` setting) to use the same credentials as `git fetch` and `git push`. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
This addresses #1409
One strange thing in my fix may be the setting and unsetting of http.dummy variable. This is a work-around for Git config problem described here:
https://stackoverflow.com/questions/37147475/gitconfig-section-duplicates-everytime-i-set-a-preference
Without this trick the installer was leaving one empty [http] section. Everything else was working fine, but system config file looked ugly.
This is my first contribution to Git for Windows, please be forgiving :)