[quicwg/base-drafts] Retry integrity protection should not add new requirements to TLS API (#3366)
Kazuho Oku <notifications@github.com> Sun, 19 January 2020 02:57 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 7ACA5120043 for <quic-issues@ietfa.amsl.com>; Sat, 18 Jan 2020 18:57:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 5Psn95hSfVjZ for <quic-issues@ietfa.amsl.com>; Sat, 18 Jan 2020 18:57:31 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70AB9120025 for <quic-issues@ietf.org>; Sat, 18 Jan 2020 18:57:31 -0800 (PST)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id D618D960501 for <quic-issues@ietf.org>; Sat, 18 Jan 2020 18:57:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1579402649; bh=xE2QVMphxafSGbO4Z7mXBwxGXF1hnw+10QZNmts+Z3A=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=xop8qWC9gT35gU9WCmPuD8/5uyYSpdMFWbctdauoCyiNEWx2KLXOmOVgxmGeYB6bd mBduPkgqWMANPe0lTMKkRWQe3FaI9E3NPHR0yi+ROHAtr9rFRCr6YJeT3yc12tRvNP uIx/LmYw8R0UlsdSquoz70ZJgKK6Hdu5u5HxyiyQ=
Date: Sat, 18 Jan 2020 18:57:29 -0800
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5GQZIV55TWLXPSSTV4GD4BTEVBNHHCBZFNCI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3366@github.com>
Subject: [quicwg/base-drafts] Retry integrity protection should not add new requirements to TLS API (#3366)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e23c599c4459_b133fde3f6cd95c2980dc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/oV2uufDLIYnaCBY3ZBnIXenUk0M>
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: Sun, 19 Jan 2020 02:57:34 -0000
Retry integrity protection (#3120) specifies the AES-GCM key and IV directly. While that works fine for people using TLS stacks that provide direct access to AES-GCM, it does not for people using TLS stacks that only provides access to TLS AEAD API. I think we can resolve the concern by simply changing the hard-coded AES-GCM key and IV we specify in the TLS draft to a set of values that can be derived by using the TLS AEAD API. -- 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/3366
- [quicwg/base-drafts] Retry integrity protection s… Kazuho Oku
- Re: [quicwg/base-drafts] Retry integrity protecti… Martin Thomson
- Re: [quicwg/base-drafts] Retry integrity protecti… Kazuho Oku
- Re: [quicwg/base-drafts] Retry integrity protecti… Jana Iyengar
- Re: [quicwg/base-drafts] Retry integrity protecti… Martin Thomson