Re: [quicwg/base-drafts] Endpoints cannot verify padding (#4253)

Martin Thomson <notifications@github.com> Tue, 20 October 2020 14:34 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE9223A0A68 for <quic-issues@ietfa.amsl.com>; Tue, 20 Oct 2020 07:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w_c3ao0Tf9vy for <quic-issues@ietfa.amsl.com>; Tue, 20 Oct 2020 07:34:39 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6CB43A0A64 for <quic-issues@ietf.org>; Tue, 20 Oct 2020 07:34:39 -0700 (PDT)
Received: from github.com (hubbernetes-node-40533ca.ac4-iad.github.net [10.52.103.61]) by smtp.github.com (Postfix) with ESMTPA id 21F9B560FA3 for <quic-issues@ietf.org>; Tue, 20 Oct 2020 07:34:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1603204479; bh=2uWN61AeLBZ9bemwuvwVLavmdOR0l22AnO88E/wIroc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aK+fJXs7KTxkjnlQvfhCPKhLllS2sRUrkrw/G3CWczTuizrHRk8Cf7SyEb4ycuqKR Xjxy2b+MN+i0KX+spfwaFg1Fej4AetynZLmDId6md5Bz5l5IJEkPqW026nCjK+w3aq 4xJudsuXIBK0bs6vT/ziIdeYvDUgyGTo16YmxAtQ=
Date: Tue, 20 Oct 2020 07:34:39 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7LCJXMKX4MV4HAMIF5TLLH7EVBNHHCWOBQMQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4253/712898555@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4253@github.com>
References: <quicwg/base-drafts/issues/4253@github.com>
Subject: Re: [quicwg/base-drafts] Endpoints cannot verify padding (#4253)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f8ef57f1dfd0_4719b438294e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/YjTmJCxW_4d1efSBgrXXN4u2UaY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 14:34:41 -0000

Agree with Ian.  My plea for stopping was not about the fix (the fix here is good), but the original change.  We would not have had this problem if we were able to accept that the protocol wasn't absolutely perfect.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4253#issuecomment-712898555