-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Cargo: "The SSL certificate is invalid" for GitHub under Ubuntu 10.04 #598
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
Comments
This is likely because ubuntu 12+ have openssl 1.0.1 and ubuntu 10 has 0.9.8, still investigating... |
This *should* help with rust-lang#598, but I'd like to confirm that it's fixed with a snapshot before marking it as fixed.
I think I found where the certs are located. |
A workaround from @alexcrichton: export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt |
This *should* help with #598, but I'd like to confirm that it's fixed with a snapshot before marking it as fixed.
Confirmed fixed by #600! |
Excellent! And thank you. |
Still having the same issue on Ubuntu 16.04 |
Encountered the same issue with the cargo binaries for linux 64 bit on Debian 9.2 The workaround mentioned above still works:
|
@WhoAteDaCake and @bluehood mind opening a new issue with more details? That'll hopefully get more visibility as I think more people would follow new issues than 3 year old issues :) |
@alexcrichton sure thing |
I encountered this issue today on Arch Linux (4.16):
I tried
but without success. |
Has your clock drifted significantly? That error is saying that your computer thinks crates.io's certificate is issued in the future. |
Yeah, my local time is incorrectly set in my arch linux. It works after fixing. Thanks |
Found while working on emk/heroku-buildpack-rust on Heroku, which runs 10.04. Folks at Heroku verify it deploys fine with 14.04, and it works locally with 12.04.
Thank you for looking at this!
The text was updated successfully, but these errors were encountered: