-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build: update all LetsEncrypt sites to HTTP challenges #23627
Comments
Change https://golang.org/cl/90915 mentions this issue: |
Updates golang/go#23627 Change-Id: Iaf24b403e12266e7c426bf6311b7f20f9cc6df83 Reviewed-on: https://go-review.googlesource.com/90915 Reviewed-by: Andrew Bonventre <andybons@golang.org>
Change https://golang.org/cl/91235 mentions this issue: |
Updates golang/go#23627 Change-Id: Ice459e272c0d55a2bf27891aa8a97338e14d1d52 Reviewed-on: https://go-review.googlesource.com/91235 Reviewed-by: Andrew Bonventre <andybons@golang.org>
Change https://golang.org/cl/91495 mentions this issue: |
…etes This makes HTTP challenges work on https://http2.golang.org/ since LetsEncrypted disabled the TLS-SNI challenges. Also, move it from a systemd unit on CoreOS to GKE. Updates golang/go#23627 Fixes golang/go#23034 Change-Id: Id8348e9e56ab43e277f1e12d563fd8fc490d6211 Reviewed-on: https://go-review.googlesource.com/91495 Reviewed-by: Andrew Bonventre <andybons@golang.org>
Change https://golang.org/cl/91518 mentions this issue: |
Updates golang/go#23627 Change-Id: I9dff655b531dc3491419ee1883c570c0bc5d8955 Reviewed-on: https://go-review.googlesource.com/91518 Reviewed-by: Andrew Bonventre <andybons@golang.org>
Change https://golang.org/cl/106455 mentions this issue: |
We need to update the following sites from TLS-SNI to HTTP ACME challenges:
beta.golang.org is the first to expire, at Feb 9th.
tip.golang.org is next at Feb 26th.
/cc @andybons
The text was updated successfully, but these errors were encountered: