-
Notifications
You must be signed in to change notification settings - Fork 18k
website: use sha256 on download page #12057
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
Labels
Milestone
Comments
CC @adg |
I agree that we should replace SHA-1 in the long term, but it's still okay for this release. For Go 1.6 we should look into a different checksum. |
SHA256. |
CL https://golang.org/cl/18353 mentions this issue. |
CL https://golang.org/cl/18354 mentions this issue. |
adg
added a commit
to golang/tools
that referenced
this issue
Jan 7, 2016
Fixes golang/go#12057 Change-Id: I2e0a27c96f3f13478a079765b8c363c9f3919c48 Reviewed-on: https://go-review.googlesource.com/18354 Reviewed-by: Russ Cox <rsc@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Given that sha1 is effectively obsolete (at the very least officially deprecated), please consider listing the sha256 checksums on the Go download page in place of or addition to the sha1 checksums currently listed on download page.
I apologise in advance if bugs relating to the website should be filed elsewhere; it was not immediately obvious where to file them.
The text was updated successfully, but these errors were encountered: