You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLS 1.3 is available on an opt-out basis in Go 1.13. When Consul is updated to use the 1.13.x version of Go will the application be updated to support TLS 1.3?
Builtin HTTPS Health checks fail if the minimum TLS version for a service is 1.3, it would be nice not to have to use an external python script in these circumstances
The text was updated successfully, but these errors were encountered:
Thanks for creating the issue @zeroflaw. We'd love to support TLS 1.3 once we upgrade and I'm not aware of any reason we'd opt out of that at this point. We'll check of course there are no risks or compatibility issues present if we do.
The blocker for now though is that Go 1.13 broke some of our Go module support and tooling so that we can't actually build Consul with it just yet. It shouldn't be anything major but is the reason we've not already upgraded the Go version.
Feature Description
TLS 1.3 is available on an opt-out basis in Go 1.13. When Consul is updated to use the 1.13.x version of Go will the application be updated to support TLS 1.3?
https://golang.org/pkg/crypto/tls/
Use Case(s)
Builtin HTTPS Health checks fail if the minimum TLS version for a service is 1.3, it would be nice not to have to use an external python script in these circumstances
The text was updated successfully, but these errors were encountered: