Re: [quicwg/base-drafts] Server cannot proceed after invalid Retry token (#3396)
MikkelFJ <notifications@github.com> Wed, 11 March 2020 17:10 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 3628F3A0E5D for <quic-issues@ietfa.amsl.com>; Wed, 11 Mar 2020 10:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level:
X-Spam-Status: No, score=-3.471 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-1.463, 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 pzN-Zr-HpO8Y for <quic-issues@ietfa.amsl.com>; Wed, 11 Mar 2020 10:10:50 -0700 (PDT)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 753DF3A0E57 for <quic-issues@ietf.org>; Wed, 11 Mar 2020 10:10:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=VV6+XOcJ8Ac1rzFK44K+D5xlC1VlZ6drs92p0Qc4fNo=; b= gD1ZK6WKKiEg5ILJSlXhanxKV7kk7BW1Iw1EujZ6oU/BES0+bAFT0aVF+XVbbz0A 0hgkhj93kta6z0xI45Wjpu19jp6iqPq1gxhoq7wPVpJRvK+rlm2U9Gp8LmokRKgQ uRxXfMakFSLiVtI267ZPEcPviOARYB83IJbxU0beLF0=
Received: by filter0886p1las1.sendgrid.net with SMTP id filter0886p1las1-10694-5E691B98-21 2020-03-11 17:10:48.975634591 +0000 UTC m=+66758.777669052
Received: from github-lowworker-819f804.cp1-iad.github.net (unknown [140.82.115.65]) by ismtpd0010p1iad2.sendgrid.net (SG) with ESMTP id JkFCrwWBR1ipJW5lPmRuNQ for <quic-issues@ietf.org>; Wed, 11 Mar 2020 17:10:48.880 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-819f804.cp1-iad.github.net (Postfix) with ESMTP id D7C5E360646 for <quic-issues@ietf.org>; Wed, 11 Mar 2020 10:10:48 -0700 (PDT)
Date: Wed, 11 Mar 2020 17:10:49 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4QTTIEBDCNKYWOBT54OT6JREVBNHHCCIN5SE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3396/597755751@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3396@github.com>
References: <quicwg/base-drafts/issues/3396@github.com>
Subject: Re: [quicwg/base-drafts] Server cannot proceed after invalid Retry token (#3396)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e691b98d5a75_73a23fcc60acd96c75088"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak15520alMj1bUtfyP1o8CatoIoN9xrye3eylw OZwExyMe1Nf0y6JO9g1cTT1R1+FcLtrfBinkaMuWB6FtZf521aIF4tFTirEQu8TF09FT24VUtgimrJ bp7XhcuqNEaaj+3fp1DXe+wfxWsLJ9zqa53qG9k6/eIIvy8v7prFx8B/1gzoQ9rUcPVrzJNhCAParZ s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/GLkfKh4ezsewoGUPXM6QJFXWpEM>
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: Wed, 11 Mar 2020 17:10:52 -0000
The resolution to send INVALID_TOKEN error could be used to attack tokens through timing attacks. It may be better to drop the packet or to require some attack mitigation measure. -- 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/3396#issuecomment-597755751
- [quicwg/base-drafts] Server cannot proceed after … Dmitri Tikhonov
- Re: [quicwg/base-drafts] Server cannot proceed af… Kazuho Oku
- Re: [quicwg/base-drafts] Server cannot proceed af… Martin Thomson
- Re: [quicwg/base-drafts] Server cannot proceed af… MikkelFJ