IETF Logo Mail Archive

Re: [quicwg/base-drafts] rate-limiting of CID issuance needs to be allowed (#2436)

Kazuho Oku <notifications@github.com> Thu, 07 February 2019 08:47 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 A10841310F7 for <quic-issues@ietfa.amsl.com>; Thu, 7 Feb 2019 00:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level:
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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_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 plfwgBhZ_pBH for <quic-issues@ietfa.amsl.com>; Thu, 7 Feb 2019 00:47:39 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F63A1310F5 for <quic-issues@ietf.org>; Thu, 7 Feb 2019 00:47:39 -0800 (PST)
Date: Thu, 07 Feb 2019 00:47:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549529258; bh=YoB7mj2bDSCVAUTsrPTxPxosJGZQ0E9B3hlCeto/avA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=p80V8pPmH2PvyGF/rscmx4+yIIMlM+CEQOWhm9mGTJfCfFcQygaLGpIo06QEGxI4C Q4ddPoJP4U5X4ebCDlwubTzX3INmXOLkmYDx9enZMNj3OAswP1K0u36im66xAbuc7t YXOT5QiK7bnXx9LxrDxjS3g4rd9/K9pQT0HgitEQ=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab45a193315c9489d728fd6a203cf481f4936b1b6092cf000000011873b2aa92a169ce184b1573@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2436/461333247@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2436@github.com>
References: <quicwg/base-drafts/issues/2436@github.com>
Subject: Re: [quicwg/base-drafts] rate-limiting of CID issuance needs to be allowed (#2436)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5bf0aa5b184_44703fcaf58d45b41090f8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/mfxsZJBqGEs56cc4VA5LjvZenIA>
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: Thu, 07 Feb 2019 08:47:41 -0000

@mikkelfj I do not think that's a viable option, because a stateless reset token cannot be tied to a particular client IP address.

Assuming that the server ties CID’s to 5-tuples, an attacker that observes the CID can send a packet carrying that CID from a different client address to obtain the stateless reset token, then use that to terminate a connection.

-- 
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/2436#issuecomment-461333247

v2.23.0 | Report a Bug | By Email