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
Any chance this issue could be resolved any time soon? This is becoming more relevant now that crypto/tls is gaining QUIC support (#44886), since QUIC only uses TLS 1.3.
For reference, I've made the equivalent change to my crypto/tls fork for quic-go in quic-go/qtls-go1-20@a42b12e. With #60107, I finally won't need to fork crypto/tls any more, so it would be nice to have this in crypto/tls.
dmitshur
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
May 25, 2023
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Set
tls.Config.MinVersion
totls.VersionTLS13
and use that config to perform a TLS handshake.What did you expect to see?
The server should see that
tls.ClientHelloInfo.CipherSuites
is set totls.defaultCipherSuitesTLS13NoAES
.What did you see instead?
The servers sees TLS 1.2 cipher suites in
tls.ClientHelloInfo.CipherSuites
.#49293 fixes this bug.
The text was updated successfully, but these errors were encountered: