Open Bug 1304245 Opened 9 years ago Updated 3 years ago

Changes to SNI after resumption are OK

Categories

(NSS :: Libraries, defect, P3)

Product:
NSS
Component:
Libraries
Type:
defect

Tracking

(Not tracked)

People

(Reporter: mt, Unassigned)

Details

We can just fall back to a full handshake. This might be more relevant if we consider connection coalescing.
Priority: -- → P3
See https://github.com/tlswg/tls13-spec/pull/1080 for more on this topic. I think that we should be OK to resume regardless of what the SNI said. We should just be careful to update the SNI to match what the client sends us (rather than copying from the session).
Summary: Don't fail if the SNI doesn't match the session → Changes to SNI after resumption are OK
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.