-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
TLS 1.3 #2080
Comments
Waiting for Go to implement it into their standard library. Fortunately, @FiloSottile -- who already implemented an earlier draft of TLS 1.3 in Go -- now works on the Go team doing cryptography. Sooooo I'm pretty confident it could happen by Go 1.11 or definitely Go 1.12. (Right? 😉) |
They seem to be aiming for go 1.12 |
Yep. We're looking at ~Feb. 2019 I think. |
Uuh, so late?? |
Stability over speed, when it comes to things like this... |
To get it in 1.11 we would have to mail it all by the end of the month, which was deemed way too tight. https://github.com/golang/go/wiki/Go-Release-Cycle |
I've compiled Caddy together with the https://www.hnrk.io/md/2._caddy+TLS1.3.md. Patch of caddy (pretty-printed) is here. TLS1.3 version is RFC8446. PoC is https://www.hnrk.io/ (SSLLabs) |
Hi, Matt, sorry for chatting in caddy repo, but @henrocker seems there is no https://golang.org/src/crypto/internal/ now. |
@vladbondarenko This is why here, I stated, that golang 1.10.4 is needed for this. |
Updated the tutorial in regards to the golang upgrade 1.11.1 in tls-tris, as well as edited my comment above. |
Thanks. That works on Centos7 also. |
@vladbondarenko Done! |
The official patch for TLS1.3 support has been merged: golang/go#9671. |
If you don't want to wait for a new version of Caddy with TLS1.3 support, you just have to install golang from the source code (git) and then build caddy with the patch of @henrocker:
|
@unixfox yeah i did it, workes fine |
Done in #2399. Go 1.12 now required to build Caddy. |
I could not find an open issue, and I hope it is not already implemented, but TLS 1.3 support should be added!
TLS 1.3 is finalized AFAIK, browsers are soon going to implement the latest "draft" (not a draft now anymore, don't know the name).
The text was updated successfully, but these errors were encountered: