Skip to content
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

Closed
bradfitz opened this issue Jan 30, 2018 · 5 comments

Comments

Projects
None yet
2 participants
@bradfitz
Copy link
Member

commented Jan 30, 2018

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

@bradfitz bradfitz self-assigned this Jan 30, 2018

@gopherbot gopherbot added this to the Unreleased milestone Jan 30, 2018

@gopherbot gopherbot added the Builders label Jan 30, 2018

@gopherbot

This comment has been minimized.

Copy link

commented Jan 30, 2018

Change https://golang.org/cl/90915 mentions this issue: cmd/pubsubhelper: enable HTTP ACME challenges

gopherbot pushed a commit to golang/build that referenced this issue Jan 31, 2018

cmd/pubsubhelper, maintner/maintnerd: enable HTTP ACME challenges
Updates golang/go#23627

Change-Id: Iaf24b403e12266e7c426bf6311b7f20f9cc6df83
Reviewed-on: https://go-review.googlesource.com/90915
Reviewed-by: Andrew Bonventre <andybons@golang.org>
@gopherbot

This comment has been minimized.

Copy link

commented Jan 31, 2018

Change https://golang.org/cl/91235 mentions this issue: cmd/coordinator: enable HTTP ACME challenges

gopherbot pushed a commit to golang/build that referenced this issue Jan 31, 2018

cmd/coordinator: enable HTTP ACME challenges
Updates golang/go#23627

Change-Id: Ice459e272c0d55a2bf27891aa8a97338e14d1d52
Reviewed-on: https://go-review.googlesource.com/91235
Reviewed-by: Andrew Bonventre <andybons@golang.org>
@gopherbot

This comment has been minimized.

Copy link

commented Feb 1, 2018

Change https://golang.org/cl/91495 mentions this issue: http2/h2demo: enable HTTP ACME challenges, move from CoreOS to Kubernetes

gopherbot pushed a commit to golang/net that referenced this issue Feb 1, 2018

http2/h2demo: enable HTTP ACME challenges, move from CoreOS to Kubern…
…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>
@gopherbot

This comment has been minimized.

Copy link

commented Feb 1, 2018

Change https://golang.org/cl/91518 mentions this issue: cmd/tip: enable HTTP ACME challenges

gopherbot pushed a commit to golang/tools that referenced this issue Feb 2, 2018

cmd/tip: enable HTTP ACME challenges
Updates golang/go#23627

Change-Id: I9dff655b531dc3491419ee1883c570c0bc5d8955
Reviewed-on: https://go-review.googlesource.com/91518
Reviewed-by: Andrew Bonventre <andybons@golang.org>
@gopherbot

This comment has been minimized.

Copy link

commented Apr 11, 2018

Change https://golang.org/cl/106455 mentions this issue: cmd/godoc: support http-01 ACME challenge in optional autocert support

bradfitz added a commit to bradfitz/build that referenced this issue Feb 1, 2019

cmd/tip: enable HTTP ACME challenges
Updates golang/go#23627

Change-Id: I9dff655b531dc3491419ee1883c570c0bc5d8955
Reviewed-on: https://go-review.googlesource.com/91518
Reviewed-by: Andrew Bonventre <andybons@golang.org>

@golang golang locked and limited conversation to collaborators Apr 11, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.