IETF Logo Mail Archive

Re: [quicwg/base-drafts] Is Retry a new connection or what? (#2180)

Martin Thomson <notifications@github.com> Fri, 14 December 2018 02:07 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 BE000130F56 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 18:07:02 -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 LTOAaxRyOEi6 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 18:07:01 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AB29130F58 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 18:07:01 -0800 (PST)
Date: Thu, 13 Dec 2018 18:07:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544753220; bh=+KgZ5p4KgDX4iAo8fdCsh86BiRDQaU9oiJW6kgT6Xg4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FPauxOvlPT3bqgWEsplqqnhzqktV7wYD9FuaUTDfgXmIVl48+r7Xi45IgeiPBlaF+ YuoePuRze2JPzgnQBBLZlPkOoo1tcZFdei//cOhzHERHrSYLwYM3dN1hqQ2PDdhO88 aPI5nOd+9q8G3L0yDM+sJUgYlznnk8S113rcFh/E=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc31793480178c9d8c9100b416b5ab91128b6349a92cf00000001182ad24492a169ce174d10b9@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2180/447188104@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2180@github.com>
References: <quicwg/base-drafts/issues/2180@github.com>
Subject: Re: [quicwg/base-drafts] Is Retry a new connection or what? (#2180)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c13104421719_7f653fd4f6ad45c025443"; 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/2IifaIwn6C0-_vLN2tyV4wxeGuY>
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, 14 Dec 2018 02:07:03 -0000

I think that it's OK to resend the same cryptographic handshake message.  The semantics of Retry mean that the first wasn't used.

The only thing that might be a concern is if an attacker can use this to cause two parallel connections to be established from the same ClientHello.  I don't think that's possible, and the protocol is structured in a way that avoids that.

(Your point about reuse and PQ does make me think that the stuff @kazuho was contemplating as a defense against packet injection is potentially dangerous in that context.  I'm glad that there are now other approaches being contemplated for that.)

-- 
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/2180#issuecomment-447188104

v2.23.0 | Report a Bug | By Email