Re: [quicwg/base-drafts] Spoofed retry token attack on IP authentication (#2394)

ekr <notifications@github.com> Wed, 22 May 2019 13:50 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 95F4F12012E for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 06:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level:
X-Spam-Status: No, score=-6.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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 q0NFnnhxjkBc for <quic-issues@ietfa.amsl.com>; Wed, 22 May 2019 06:50:23 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACA1B12013A for <quic-issues@ietf.org>; Wed, 22 May 2019 06:50:23 -0700 (PDT)
Date: Wed, 22 May 2019 06:50:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1558533023; bh=ASwlvoWwL7eP3z/LOF7BUporF5RPNMkqjnZ0VIP5mgE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uNdOKp4f9C79HNGbFo5+b+VYb3IcCT3KBxQCTbaT4DcxBlAiCvWS8RJm8e/25AeIB QYQW8E5Lnz+Jjk0q7v8amMe208PxcDusPIjpbpoyCfX2JV0MnkD1SFQkUmixJsdRVK dINEDRPyvy/55Prnn8vBquB9BIJ91qCURVGk8ogU=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZYK55X6BOVCXLVQSN26KDB5EVBNHHBQI6HYI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2394/494811039@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2394@github.com>
References: <quicwg/base-drafts/issues/2394@github.com>
Subject: Re: [quicwg/base-drafts] Spoofed retry token attack on IP authentication (#2394)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ce5539ecbc3b_12ef3feab56cd95c10133e0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/A8h3fg5DGuxsj3rOaAESf_kE9qU>
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, 22 May 2019 13:50:25 -0000

Discussion on London: I think this misunderstands the purpose of the retry token.

As a practical matter, we assume that servers under normal conditions respond to Initial with a full first flight. Otherwise, QUIC is a two-round trip protocol no better than TCP. So, there is a builtin 3x amplification attack on random victims.

The purpose of the retry token is when the *server* is under attack from spoofed packets, and wants to efficiently distinguish between true and false IPs so it can blacklist the attackers. A retry token collection attack is possible here too, but the anti-DoS system has to track IPs anyway, and so can just track any IP address which is associated with excessive traffic anyway.

Proposal: Close with no action.

-- 
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/2394#issuecomment-494811039