Currently I have the following entry in my .gitconfig
in my user directory.
...
[http]
sslCAInfo=C:\\Users\\julian.lettner\\.ssh\\git-test.pem
...
This sets the certificate to use when interacting with the git server (required by my company's git server).
But now I cannot clone other repositories (for example a public repository on GitHub), because the client always uses the configured certificate which gets rejected by other servers.
How can I circumvent this certification issue? Can I configure Git to use the Windows Certificate Store to authenticate?
Beginning with Git for Windows 2.14, you can now configure Git to use SChannel, the built-in Windows networking layer. This means that it will use the Windows certificate storage mechanism and you do not need to explicitly configure the curl CA storage mechanism.
From the Git for Windows 2.14 release notes:
You can choose the new SChannel mechanism during the installation of Git for Windows 2.14. You can also update an existing installation to use SChannel by running:
Once you have configured this, Git will use the Windows certificate store and should not require (and, in fact, should ignore) the
http.sslCAInfo
configuration setting.Use:
To specify per-repository settings. Local settings are stored in the
.git
directory.An overview of the three locations where
git
can store settings:--local
: Repository specific,<repo_dir>/.git/config
--global
: User-specific,~/.gitconfig
--system
: System default,/etc/gitconfig
More specific ones override more general settings, i.e. local overrides both global and system.