-
Notifications
You must be signed in to change notification settings - Fork 475
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
x509 Certificate issue #45
Comments
Can you still reproduce this, @gipfeli? WWO recently changed their certificate and it works for me. Which commit of wego are you using? |
|
Two possibilities come to mind:
A dirty workaround would be to change the |
I've just started hitting this issue too on Ubuntu 14.10 with the latest version of ca-certificates |
Heyho @gipfeli, @Region51, @thomshutt, can you check if it works, when you insert the line Also which version of golang-go are you running? |
On my mac (10.10.3) I have the following SHA checked out e0dce56 (10 days ago).
|
I synced my repo to master head, and added the line |
Same here, all working after adding crypto/sha512 |
All working. We can close the ticket now. |
The issue is also fixed upstream, but I don't know in which version exactly. I am running golang 1.4.2, but debian jessie is still at 1.3.3. Im closing it, but if there are more reports from up-to-date distro users, I think we have to include that import statement in wego master temporarily, until the major distributions caught up on the golang upstream fix. |
Reopened, so people see this. Still if anyone having this problem is running an up to date distribution, let me know. |
ubuntu 14.04 lts, will be "up to date" for a few years more... go version go1.2.1 linux/amd64 installed from your github, now 5 hours ago (thats as upstream as it gets, right?). plus: very latest security updated ssl/tls libraries. |
Ok, Ubuntu seems to be not bleeding edge enough unfortunately… |
Maybe adding 'x509 Certificate issue' will solve it?
The text was updated successfully, but these errors were encountered: