-
Notifications
You must be signed in to change notification settings - Fork 18.7k
Closed
Labels
FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.
Milestone
Description
What version of Go are you using (go version)?
The bug impacts following versions
- Go1.19.6 or later
- Go1.20.1 or later
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
The bug is not OS dependent
What did you do?
- I have written TLSv1.3 client and server written in go.
- In the server I have set
CurvePreferenceswith non-default list of curves. - In the client I'm using default list of curves.
- In the client I have enabled TLS session resumption by setting
ClientSessionCache
What did you expect to see?
When the client establishes second TLS session, I expected the TLS handshake to succeed.
What did you see instead?
When the client establishes second TLS session, the server will reject it with alert invalid PSK binder.
tgrosinger
Metadata
Metadata
Assignees
Labels
FrozenDueToAgeNeedsFixThe path to resolution is known, but the work has not been done.The path to resolution is known, but the work has not been done.