Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

quictls server should treat reception of a non-empty legacy_session_id in ClientHello as error #29

@tatsuhiro-t

Description

@tatsuhiro-t

It looks like quictls server accepts non-empty legacy_session_id in ClientHello.
Meanwhile, https://tools.ietf.org/html/draft-ietf-quic-tls-34#section-8.4 says that:

A server SHOULD treat the receipt of a
TLS ClientHello with a non-empty legacy_session_id field as a
connection error of type PROTOCOL_VIOLATION.

Here is how boringssl handle this:
https://github.com/google/boringssl/blob/7a1986c463548627b83ed58d9f9db65bddbce6a5/ssl/tls13_server.cc#L198

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions