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
Upgrading to OSX 10.12.1 breaks the ability to "go get" packages from gopkg.in #47
Comments
I am receiving this same error but on a different version of OSX (
EDIT: This looks to be working now? |
+1 |
Same here |
Can you please try this:
|
@niemeyer |
I'm probably missing something fundamental about this problem.. why would you like to disable verification? |
I had the same issue too:
Adding the git config line @niemeyer mentioned fixed it for me. |
@niemeyer - If I recall correctly, I had to disable ssl verification in order to access some NPM packages on a server using self-signed certificates and for getting around a corporate firewall that rewrote certificates. |
I'm sure this is obvious to most people here, but it must be said: replacing TLS certificates or disabling their verification pretty much kills the point of using TLS. I'd strongly encourage not doing that. At the same time, I don't understand what the deal is with the TLS library being used by git in your systems. If the certificate is valid when it checks it, how can it possibly break when it's not checking it? I'm closing this issue, as it doesn't look like a problem on gopkg.in. |
Thank You. @niemeyer |
Yes, per notes above, git client on Mac apparently breaks when not validating a valid certificate. Just enable validation (it's a good idea, btw!) and it works. |
That's not accurate. When sslVerify is false I can
Perhaps it is the type of ssl certificate in use that the Mac git client struggles with, but it works fine not validating valid certificates other than the gopkg cert. |
Yes, the fact it works with other certificates doesn't say much. Is the certificate valid? Yes. Does it work when that same git client validates it? Yes. Does it work on every other browser and every other git client? Yes. So, all evidence points to a bug on the client. I'm obviously still open to any information that would say otherwise. |
git config --global http.sslVerify true will resolve SSL errors |
fantastic |
Can not get packages like
go get gopkg.in/alecthomas/kingpin.v2
. It will fail with the following error:Unknown SSL protocol error in connection to gopkg.in:-9838
The text was updated successfully, but these errors were encountered: