Re: [quicwg/base-drafts] Use the same KDF regardless of TLS version (#2034)
ekr <notifications@github.com> Fri, 23 November 2018 04:25 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 3549F130DE0 for <quic-issues@ietfa.amsl.com>; Thu, 22 Nov 2018 20:25:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 oAEE2nDyt_ss for <quic-issues@ietfa.amsl.com>; Thu, 22 Nov 2018 20:25:22 -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 DA251126DBF for <quic-issues@ietf.org>; Thu, 22 Nov 2018 20:25:21 -0800 (PST)
Date: Thu, 22 Nov 2018 20:25:20 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542947120; bh=398JiltZhEVdBdu7HZNMMLrvm5bht43mGuYmY0SZbHc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k58OmSsnSc7Kon2DQKn+p/P6YrMOknBFRYMCnD0j6IFSf29vQmsuv1aVwBzAv039+ HUN0f4UYtH20Qbviziu16mart0uTj4qskY19WVV+45ZhJbcLFEJJ8MAt7rlhbCv2Mr a6WNz7urWSUpLYFsRkTfHALL6ypznYARoWLj9yZQ=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab03e68555b8e3ed5c23350987a62eeb180c741a1e92cf00000001180f433092a169ce16d3c410@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2034/c441154247@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2034@github.com>
References: <quicwg/base-drafts/pull/2034@github.com>
Subject: Re: [quicwg/base-drafts] Use the same KDF regardless of TLS version (#2034)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf78130ddad5_7a383f9b724d45c053306c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/YqhMqPqefx2RYUtC9Vz7ebjMo6c>
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: Fri, 23 Nov 2018 04:25:23 -0000
> I don't think that the collision argument is particularly relevant, because we ensure that QUIC is the exclusive user of the secret (something I think that we want to stipulate). The issue here is separation between TLS and QUIC handshakes. The reason (I assume) that you are using the "quic " labels in key derivation is to ensure that the QUIC traffic keys can never be the same as the TLS ones, even though they are derived from the same secret.. However, this isn't the case if you have no idea what the TLS KDF is, as it could perversely use the "quic " labels -- 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/2034#issuecomment-441154247
- [quicwg/base-drafts] Use the same KDF regardless … Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… Kazuho Oku
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… Kazuho Oku
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… Kazuho Oku
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… janaiyengar
- Re: [quicwg/base-drafts] Use the same KDF regardl… Marten Seemann
- Re: [quicwg/base-drafts] Use the same KDF regardl… Alessandro Ghedini
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… ekr
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… MikkelFJ
- Re: [quicwg/base-drafts] Use the same KDF regardl… ekr
- Re: [quicwg/base-drafts] Use the same KDF regardl… Martin Thomson