[quicwg/base-drafts] Stateless Reset needs "on-path" proof (#1230)

Igor Lubashev <notifications@github.com> Sun, 18 March 2018 18:46 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 44778127444 for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 11:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.392
X-Spam-Level:
X-Spam-Status: No, score=-0.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 J2DxMeSWzywt for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 11:46:18 -0700 (PDT)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (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 E8AC2127136 for <quic-issues@ietf.org>; Sun, 18 Mar 2018 11:46:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=tDcN2dPG7QufpghHRUO+c68NTEc=; b=tVpfoijDxOnmzzMV ed1D3xeXXL0lLLWJtbMDeWiVr7QG6WErpgp2DkbI9ngKndFzYyokas99qnlXHj0h xqqbqFvCvHw4Pn7xqXbxgQOmZoyBOz6mxDJzLykFc+cqobP9GsotHfFN9n6O0Ea4 L2az/+YGG6awXjvVD6q5ViRazTY=
Received: by filter0205p1iad2.sendgrid.net with SMTP id filter0205p1iad2-5629-5AAEB3F8-1A 2018-03-18 18:46:16.534601713 +0000 UTC
Received: from smtp.github.com (out-2.smtp.github.com [192.30.252.193]) by ismtpd0025p1mdw1.sendgrid.net (SG) with ESMTP id yifaMavLSXy__qgRaGfTXA for <quic-issues@ietf.org>; Sun, 18 Mar 2018 18:46:16.342 +0000 (UTC)
Date: Sun, 18 Mar 2018 18:46:16 +0000
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0956fe47121933e823c497cbb3cbc5470ac77af492cf0000000116c675f892a169ce12414b9e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1230@github.com>
Subject: [quicwg/base-drafts] Stateless Reset needs "on-path" proof (#1230)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aaeb3f8188fd_5d473feb202e8f387973e9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1zoV42y3p7px7sfxn5ECjjwMtDLTj+84dr+I nfYXpBC8aIXFCijr/794URWJ64oP45tEjM8QtWoLInVMRxIayJktt/p5Kwx2TrYSgFMpQLArUWyTD8 0C8iB4XiOGdWTte4WqMr1DLee/yDhYrhCWH6qDu5G1IW7St9vf7pHVvaEY4GEfzxbPfaDtbF5ZxhSb 0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/SI9LR7r0F61wT7lSxI1L4HlJIEU>
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: Sun, 18 Mar 2018 18:46:19 -0000

Stateless Reset has contains a proof that the Server sent it.  However, if the server's key is compromised, Stateless Reset can be forged wholesale off-path.  Stateless Reset must contain a proof that the sender observed the original packet that caused Stateless Reset.  Clearly, there are many simple ways to do so.

-- 
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/1230