To check if at least the clone works without checking said certificate, you can set: export GIT_SSL_NO_VERIFY=1īut that would be for testing only, as illustrated in " SSL works with browser, wget, and curl, but fails with git", or in this blog post.Ĭheck your GitLab settings, a in issue 4272. You need to check the web certificate used for your gitLab server, and add it to your /bin/curl-ca-bundle.crt. What you have to do to circumvent the problem on your computer is telling it to trust that certificate - if you don't have any reason to be suspicious about it. This doesn't mean the certificate is suspicious, but it could be self-signed or signed by an institution/company that isn't in the list of your OS's list of CAs. The basic reason is that your computer doesn't trust the certificate authority that signed the certificate used on the Gitlab server. Warning: as noted in gareththered's excellent answer, this adds all certificates, instead of only the Root CAs.īlindly adding all (any) certificate to your trustStore without due diligence is not the best course of action. Sudo bash -c "echo -n | openssl s_client -showcerts -connect $hostname:$port -servername $hostname \Ģ>/dev/null | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' \ Trust_cert_file_location=`curl-config -ca`
0 Comments
Leave a Reply. |