Re: [quicwg/base-drafts] QPACK security considerations (#3575)

afrind <> Tue, 14 April 2020 22:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 772673A11BA for <>; Tue, 14 Apr 2020 15:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CCx1zoQm4Rnd for <>; Tue, 14 Apr 2020 15:41:20 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3C7F53A11BC for <>; Tue, 14 Apr 2020 15:41:20 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 864BFE10EA for <>; Tue, 14 Apr 2020 15:41:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1586904079; bh=xw3Z35YzvM33KF6PQ/kend/fRFPMaa1EQx+wpOVKfFI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pblh3GOTuqLq1qb+da7Zr7D3tFhjOcI7vNXZ7mWZ532ADmAPXHOSwrWMAAw8MGiv8 21DlsFE5ms96m7fRyZcZWjBPofYiJ9ADbQsOHxZuo2LdBOrH5S92ONIrAW+eV2kjoN GPz40PzZ2ZCmb7ygTOR0yPINzyJWUkNLkhrEtAh0=
Date: Tue, 14 Apr 2020 15:41:19 -0700
From: afrind <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3575/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] QPACK security considerations (#3575)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e963c0f760a4_24f93fe5166cd9602873c8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Apr 2020 22:41:21 -0000

@afrind commented on this pull request.

> +On the contrary, an encoder might prefer indexing values for header fields that
+have little or no value if they were exposed. For instance, a User-Agent header
+field does not commonly vary between requests and is sent to any server. In that
+case, confirmation that a particular User-Agent value has been used provides
+little value.
+Note that these criteria for deciding to use a never indexed literal
+representation will evolve over time as new attacks are discovered.
+##. Static Huffman Encoding
+There is no currently known attack against a static Huffman encoding. A study
+has shown that using a static Huffman encoding table created an information
+leakage, however this same study concluded that an attacker could not take
+advantage of this information leakage to recover any meaningful amount of
+information (see [PETAL]).

It's mentioned in the string literal section: 

> When Huffman encoding is enabled, the Huffman
table from Appendix B of [RFC7541] is used without modification.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: