[quicwg/base-drafts] Forbid TLS-level KeyUpdate in draft-ietf-quic-tls (#1833)

David Benjamin <notifications@github.com> Thu, 04 October 2018 21:54 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 253B1130DE5 for <quic-issues@ietfa.amsl.com>; Thu, 4 Oct 2018 14:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Level:
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 RD5zq8IbYU41 for <quic-issues@ietfa.amsl.com>; Thu, 4 Oct 2018 14:54:25 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6894130934 for <quic-issues@ietf.org>; Thu, 4 Oct 2018 14:54:24 -0700 (PDT)
Date: Thu, 04 Oct 2018 14:54:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538690063; bh=sqqreoW+zGcg3/4L1gxXhp1NHwDBJpKETMAbrSLo5AA=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=jno/qWx5iJNiMvYCjIUZ5tcutims+N8BtPtMFjVhXaC4UWP+RispJ7mGbXDfe70H+ lHey2wFU21Ar4CH0OC6SomH05aEWiGHI/VbIuamH8k0fRtgi2Kx/zez9+wBTmyF6B+ ivhQ/GzcFxLz+osnTfbMIMT8jsnkyONtdI/0jM8U=
From: David Benjamin <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8ffd025fe33ff3b1cc9fad26d9d038becf53742c92cf0000000117ce4e0f92a169ce15dfc0c4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1833@github.com>
Subject: [quicwg/base-drafts] Forbid TLS-level KeyUpdate in draft-ietf-quic-tls (#1833)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bb68c0fccbc2_79c3fe5904d45bc70889e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: davidben
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/sdffYww8ZqYCl9tL_TcZRCqlgPU>
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: Thu, 04 Oct 2018 21:54:27 -0000

Since QUIC uses its own mechanism, the spec should say the TLS-level KeyUpdate MUST NOT be sent and MUST be treated as a fatal error on receive.

Otherwise an implementation may forget about this and, when TLS sees a KeyUpdate, call some callback in some weird unexpected way and confuse things.

-- 
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/1833