Add TLS 1.3 to Go and Caddy #181
Conversation
|
Hmm, what's blocking the patch from being merge into mainline? I'd love to see that be the default before we flip the bit. p.s. thanks for drafting the update! |
|
@igrigorik The developer of Caddy (@mholt) wants to wait for the next point release of Go (1.12) before merging it into mainline since compiling Caddy with TLS 1.3 support requires you to use a compiled version of Go's master branch instead of its current point release (1.11.2). To my knowledge, Go 1.12 is scheduled to be released in Feb 2019. Edit: I accidentally a word. |
|
Gotcha, thanks for the helpful context. Given that this still requires build-from-master and patches, I'd propose we wait until this work makes it into stable? |
|
@igrigorik Sure thing. I'll update this pull request once TLS 1.3 support lands in the stable versions of Caddy and Go. |
|
Thanks for the ping, and for this patch. It's a little early though 😄 All of this is correct. Shortly after Go 1.12 is released in February, Caddy will default to TLS 1.3, and we'll be tagging Caddy v1.0 sometime around then too. |
|
@igrigorik @mholt TLS 1.3 support has landed in the stable versions of Go and Caddy. Can you merge this PR now? |
|
Yep! One more thing before I merge... Now that it's live in stable, do we have doc URLs we can point to, instead of GitHub issues? |
|
By Monday we should. I will update this issue then. |
|
Looks like OPs branch is gone: @mholt proposed changes look good to me |
|
@WhaleHub Do you want to finish this up? (Where'd the repo go?) |
ghost
closed this
ghost
mentioned this pull request
|
@mholt @midzer @igrigorik I opened a new PR with the links suggested by mholt: #192 |
This PR adds support for TLS 1.3 (RFC 8446) to Go and Caddy. TLS 1.3 support was recently added to Go. Caddy is written in Go and if you compile it with the latest branch of Go and apply a tiny patch to it, Caddy also supports TLS 1.3. To see an example of a site using Caddy with TLS 1.3, click here.