I've spent quite a lot of time troubleshooting why the http.sslCAPath git config option would seemingly ignore the path that I pass to it, and turns out - passing a path is not enough, it _must_ be properly structured with a "c_rehash" (Linux) command first. The reason is: apparently Git passes this argument down to libcurl library, which in turn has certain expectations on the path structure.
After I ran "c_rehash" against my CA cert path containing a list of .pem files, I then could finally clone repos from a private bitbucket hub secured by self-signed certificate. The documentation for this option is missing the crucial point and is thus useless, quote from Git documentation at https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpsslCAPath: " http.sslCAPath Path containing files with the CA certificates to verify the peer with when fetching or pushing over HTTPS. Can be overridden by the GIT_SSL_CAPATH environment variable." It should mention the "c_rehash" procedure or at least reference the relevant libcurl documentation piece (e.g. https://curl.se/libcurl/c/CURLOPT_CAPATH.html) . Kind regards, Alex -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/2d232c05-ceda-4002-8cfc-6f4c0dc80f9bn%40googlegroups.com.
