IETF Logo Mail Archive

Re: [quicwg/base-drafts] handling of KeyUpdate in other epochs are specified in RFC 8446, do not override (#4412)

Kazu Yamamoto <notifications@github.com> Mon, 30 November 2020 05:33 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 C214C3A1007 for <quic-issues@ietfa.amsl.com>; Sun, 29 Nov 2020 21:33:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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_20=1.546, 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 a5POQFCdjFNM for <quic-issues@ietfa.amsl.com>; Sun, 29 Nov 2020 21:33:48 -0800 (PST)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E3383A1003 for <quic-issues@ietf.org>; Sun, 29 Nov 2020 21:33:48 -0800 (PST)
Received: from github.com (hubbernetes-node-4211752.va3-iad.github.net [10.48.114.42]) by smtp.github.com (Postfix) with ESMTPA id 3B500E0430 for <quic-issues@ietf.org>; Sun, 29 Nov 2020 21:33:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1606714427; bh=BYPfU+7Gv6urEhB7Z0OF7OiDD+WRErCTbyOMvDECLPQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rVtUQLIBAekJ0twJ9QD1kkX0ICqzZxWZHjrlcohvQq6bs4ESoEgzcg00NdxASEAAI DKiaZnSF9J+evqTxbeU7wMuoaWe1AVKmZwyTCxenucwf2ySytKyUKArxAwAOS6OCAh LaFkuEQjK0w6lOPhelG7JJHs/tm/NGOnPz0UvuPo=
Date: Sun, 29 Nov 2020 21:33:47 -0800
From: Kazu Yamamoto <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4LRWFEYO4SWHG6ECV52BSTXEVBNHHCZX3BKQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4412/c735556760@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4412@github.com>
References: <quicwg/base-drafts/pull/4412@github.com>
Subject: Re: [quicwg/base-drafts] handling of KeyUpdate in other epochs are specified in RFC 8446, do not override (#4412)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5fc4843b36435_4cf919b4257984"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazu-yamamoto
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/-yhWmL2-M_D37c4eD8ZHxYl-YX4>
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: Mon, 30 Nov 2020 05:33:50 -0000

@kazuho `h3spec` now supports an error case of TLS KeyUpdate in 1-RTT. Based on experiments with `h3spec`, it appeared that TLS stack might be freed already when any CRYPTOs including KeyUpdate in 1-RTT are received. So, we should also allow `PROTOCOL_VIOLATION` in this case.

-- 
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/pull/4412#issuecomment-735556760

v2.23.0 | Report a Bug | By Email