Repository navigation
feat(application): parse TLS handshake extensions #2514
Description
Follow-up split out of #2437 (owner's choice, option 1).
TLS handshake messages on main are parsed at the message-type level (ClientHello, ServerHello, Certificate, ...), and the only extension read is supported_versions, which is peeked to identify TLS/DTLS 1.3 (#2441). Every other extension is kept undecoded.
Scope: parse the extension list of ClientHello, ServerHello, EncryptedExtensions and HelloRetryRequest into typed records (RFC 8446 §4.2, IANA "TLS ExtensionType Values"), backed by a pcapkit.const registry with its vendor crawler (const-vendor-pairing). Unknown extensions stay as raw bytes. Construction and parsing must round-trip byte-exact.
Blocked: #2490's reorder is editing pcapkit/protocols/application/ssl.py, and #2457's capture check may touch the TLS modules. This unblocks when both hand back.
Activity
JarryShaw commentedon Nov 1, 2026
Still
blocked, on a new condition. #2457 closed, and #2490 does not touchssl.py(#2522 is FTP only). #2517 and #2525 are now changing howTLS.readhandles records. This unblocks when their PR merges.JarryShaw commentedon Nov 1, 2026
Unblocked: #2537 merged, so TLS's chained records are on main. Held one tick for the same fan-out width as #2489. It starts next sweep.