[TLS] Ambiguity of TLS Certificate Compression (RFC 8879)

Kazu Yamamoto <kazu@iij.ad.jp> Fri, 30 January 2026 03:46 UTC

Return-Path: <kazu@iij.ad.jp>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E068EAF41413 for <tls@mail2.ietf.org>; Thu, 29 Jan 2026 19:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iij.ad.jp
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWouK8p2Aqm0 for <tls@mail2.ietf.org>; Thu, 29 Jan 2026 19:46:50 -0800 (PST)
Received: from omgo.iij.ad.jp (mo1120.iij.ad.jp [202.232.173.188]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B544FAF41402 for <tls@ietf.org>; Thu, 29 Jan 2026 19:46:49 -0800 (PST)
DKIM-Signature: v=1;a=rsa-sha256;c=relaxed/simple;d=iij.ad.jp;h=Date: Message-Id:To:Subject:From:Mime-Version:Content-Type: Content-Transfer-Encoding;i=kazu@iij.ad.jp;s=20250414.omgo;t=1769744801;x= 1770954401;bh=2+RfPE7BSa/WaWY4Pi/vj3UpxROl/a1aCpUAwGyUKag=;b=ZqlCGH4NqIXoe/G8 5K8N94m9BCjxsMcSK4zyzBRmE04xixJLDtGGoPfY6IyG5D7laxb9BF1LfbJJYK/O/n/wAv5PGwRur p2cb0KDL582m8UwI9cHPB+IMhXEIe2Mfze5Fil7jL9GuDHqjbzIwKCRNxvbEADjs9H4/F+EnV3V79 2JsXQKVK0iWVcg3Z601fmM4jnrbg8a27l9xRAp+W9eGxpG73cPRQotDSxo2rTLkyL0Eq3aRuJsZ9O iQjjJD2kNA+8xNpb0hyZapsZxPuVJkUBWd/U350MbG4hOxHX8WeMW8CdQqSAXD2CSFPIxmnEfzFVy OUshq6cfJPh2lRkHww==;
Received: by omgo.iij.ad.jp (of-mo1120) id 60U3kffu1814220; Fri, 30 Jan 2026 12:46:41 +0900
X-ENVID: IIJ
X-Iguazu-Qid: C8OKEOpOuotqraw96O
X-Iguazu-QSIG: v=2; s=0; t=1769744801; q=C8Oiyzpq3PkBw2Yhuq; m=YBTZ1EnjHoi6GSnsSAg7knKHtKcCWs25hvFkLU/IzyI=
Date: Fri, 30 Jan 2026 12:46:40 +0900
Message-Id: <20260130.124640.484427558490648192.kazu@iij.ad.jp>
To: tls@ietf.org
From: Kazu Yamamoto <kazu@iij.ad.jp>
X-Mailer: Mew version 6.10 on Emacs 31.0.50
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: PDYDHU2LM6T42L3K6PDDI675K3TLR5E3
X-Message-ID-Hash: PDYDHU2LM6T42L3K6PDDI675K3TLR5E3
X-MailFrom: kazu@iij.ad.jp
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Ambiguity of TLS Certificate Compression (RFC 8879)
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/uUf3dIfjlZCpLD0ZTd6a_ehOosc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

Hello,

Though implementation of certificate compression, I felt that 
RFC 8879 is ambiguous on how to calculate transcript hash.

RFC 8446 defines the content for Certificate Verify as follow:

   Transcript-Hash(Handshake Context, Certificate)

This is natural reuse of transcript hash. So, AFAIK, "tlsfuzzer" and
facebook.com use the following as the content:

   Transcript-Hash(Handshake Context, CompressedCertificate)

But RFC 8879 says:

   After decompression, the Certificate message MUST be processed as
   if it were encoded without being compressed.

I think the following original interpretation is possible for the
content:

   Transcript-Hash(Handshake Context, Certificate)

Clarification would be helpful.

--Kazu