IETF Logo Mail Archive

Re: [quicwg/base-drafts] Handshake errors (#608)

janaiyengar <notifications@github.com> Tue, 19 September 2017 21:52 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 2C64A132D42 for <quic-issues@ietfa.amsl.com>; Tue, 19 Sep 2017 14:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 JF5wJMMyWAh1 for <quic-issues@ietfa.amsl.com>; Tue, 19 Sep 2017 14:52:51 -0700 (PDT)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 B8C6D132397 for <quic-issues@ietf.org>; Tue, 19 Sep 2017 14:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; 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=QKYRnccFwvADYjmmb/sLldzU4LU=; b=fZHITkocNnQy/ExS mFOZYrd/0spQaJye0jqUWHxIbkPqpQOhtzELuq0JWbXGz9r5kACg2W2XmHViNLRX ncLjJMxegEEaAix+tGRSYPbP4e4ASOwqMbPcEvRDw4Na3B002kl3mfkiTaawBWp4 H206cpzcEyONvA4uwyUCVvhPxI4=
Received: by filter0829p1mdw1.sendgrid.net with SMTP id filter0829p1mdw1-20894-59C191B1-11 2017-09-19 21:52:49.48262359 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0013p1iad2.sendgrid.net (SG) with ESMTP id lLE46_DRQQCY70lHm4-1UA for <quic-issues@ietf.org>; Tue, 19 Sep 2017 21:52:49.412 +0000 (UTC)
Date: Tue, 19 Sep 2017 21:52:49 +0000
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf6a613583c9d2fbf00a0a9e86a5558363b5cc77a92cf0000000115d953b192a169ce0df5bf15@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/608/330684602@github.com>
In-Reply-To: <quicwg/base-drafts/issues/608@github.com>
References: <quicwg/base-drafts/issues/608@github.com>
Subject: Re: [quicwg/base-drafts] Handshake errors (#608)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c191b1501fa_6ef33fe16a336f7c83286"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3PiLzLSZEjiA9iCMtazWRBj9IEvoBrAJHwOM LgOYjMKZmlc9D8GbYxur7Oyq5NwkDb5MA287gvCURrmAax+G/uRlNHBVleH4LBKO2qWeOfOx/D6v2v iU5uFtCCe5ap+bKAMgTju/1cVUrSOF77tIZgpsJTwxOtLkKPcwI5IP/KKjsR7cAO3ufOBZaG16SbG7 k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Kt_39w8vs0XBniMm7gGkzHwa_uU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 19 Sep 2017 21:52:52 -0000

Revisiting this question, I think we have a small bit of a pickle. From #645, we agreed in Prague that "Off-path attacks would be protected against by using return routeability/proof of receipt." Server Cleartext carries a brand new packet number and carries a server-chosen connection ID, which means there's no proof of receipt in this packet. We should address this.

We could simply require that a Server Cleartext packet that closes a connection MUST echo the client's connection ID. This ought to be ok, since this connection is getting torn down, so there won't be a need to use a new connection ID anyways.

-- 
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/608#issuecomment-330684602

v2.46.0 | Report a Bug | By Email | System Status