Skip to content

DTLS 1.3 Unified Header receiving packet belonging to another epoch #1912

@rsith71

Description

@rsith71

Looking at the RFC it looks like if we receive an epoch that doesn't match the current epoch then we should assume it came from a prior epoch. Right now the code in dtls get more records thinks it is coming from a future epoch.

Section 4.2.2. Reconstructing the Sequence Number and Epoch of RFC 9147

   During the handshake phase, the epoch bits unambiguously indicate the
   correct key to use.  After the handshake is complete, if the epoch
   bits do not match those from the current epoch, implementations
   SHOULD use the most recent past epoch which has matching bits, and
   then reconstruct the sequence number for that epoch as described
   above.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

New

Status

Waiting Review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions