From db1d02130df55714b4c15e4212b9b1489aa3483e Mon Sep 17 00:00:00 2001 From: Loganaden Velvindron Date: Mon, 4 Mar 2024 10:22:31 +0400 Subject: [PATCH] Mention hybrid key exchange for split TLS ClientHello Would it be worth mentioning this specific case https://tldr.fail/, where TLS ClientHello processing is not implemented correctly ? --- draft-ietf-tls-rfc8446bis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-tls-rfc8446bis.md b/draft-ietf-tls-rfc8446bis.md index c67cfb4e..dd1f561e 100644 --- a/draft-ietf-tls-rfc8446bis.md +++ b/draft-ietf-tls-rfc8446bis.md @@ -5255,7 +5255,7 @@ TLS protocol issues: - Do you correctly handle handshake messages that are fragmented to multiple TLS records (see {{record-layer}})? Do you correctly handle - corner cases like a ClientHello that is split into several small fragments? Do + corner cases like a ClientHello that is split into several small fragments such as hybrid key exchanges? Do you fragment handshake messages that exceed the maximum fragment size? In particular, the Certificate and CertificateRequest handshake messages can be large enough to require fragmentation.