Re: [quicwg/base-drafts] Does a Retry really need to change the CID? (#2837)

David Schinazi <> Mon, 24 June 2019 16:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C88A9120614 for <>; Mon, 24 Jun 2019 09:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_28=1.404, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PoIvYS4XWt7J for <>; Mon, 24 Jun 2019 09:34:42 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DE9A412060E for <>; Mon, 24 Jun 2019 09:34:41 -0700 (PDT)
Date: Mon, 24 Jun 2019 09:34:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1561394081; bh=5PGJBx/H1JBHjLaFdwZlJnd74p5aXI54pDFmLyfTKp8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=F6GQdWtLJ2yr+oI0KxBkj/Ve+Gt40d+PbuxJJB5DuM/7bClxxDGte1jQEPXRePHer YsYNIXD7A1ABK1kd86P6zEajDkvtEqueBfV22/ZP0pNX52mNysqhFs5/iMuFPEumj7 FeuWricR0TnaTsnAjEkr1pjICnADxNBCvtIsNM6E=
From: David Schinazi <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2837/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Does a Retry really need to change the CID? (#2837)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d10fba0f1dea_5e273fa3222cd9682495de"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 24 Jun 2019 16:34:44 -0000

@nibanks the retry token is part of the initial encryption associated data, so if you remove it you'll need to recompute the crypto anyway.

@marten-seemann can you elaborate on what the consequences of this attack are? It sounds like the attacker can close the connection by sending a bad retry. How is that different from having the attacker send a bad retry that changes the CID and contains a bogus retry token?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: