IETF Logo Mail Archive

Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)

MikkelFJ <notifications@github.com> Sat, 27 July 2019 08:04 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 3B20F120251 for <quic-issues@ietfa.amsl.com>; Sat, 27 Jul 2019 01:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 fD6LNlDu9WGO for <quic-issues@ietfa.amsl.com>; Sat, 27 Jul 2019 01:04:06 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88470120106 for <quic-issues@ietf.org>; Sat, 27 Jul 2019 01:04:06 -0700 (PDT)
Date: Sat, 27 Jul 2019 01:04:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1564214645; bh=eBFEr9mZyzhEe/Z08JfVX5aQPus/l2O9PnuC8Nfaxio=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ch5dk8Bu5tlYKwfGeB/yBTAb/3RvkfJJgUUp1+mh28bS0LQ9uyzgmrxs1t5lxfWtt ieQ9fC7G/EjRSsSwBfYL0nPdSBE0JSrgEh7F76dtFCLUji7C1HM/GsoYjQYkADhZX9 ncGm4+rvTbMx1XjkIhQSeUyaTFrXvBheGK2NqbtI=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZYMTMSFCGMNMHBZ3V3JE37LEVBNHHBW5BWIY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2844/515664068@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2844@github.com>
References: <quicwg/base-drafts/issues/2844@github.com>
Subject: Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d3c05757fb4d_72dc3f9eda0cd95c4254bd"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/0iXeib2tqL_vWWWJHnJOrdrOnqA>
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: Sat, 27 Jul 2019 08:04:09 -0000

> However, simply doing that could lead to an amplification attack (as we
know, the amount of data (or packets) the server can send as a reset needs
to be smaller than the amount of data that the server has received).

The main reason for this is not amplification but because it could lead to
infinite reset loops. This could be by mistake, or by deliberate injection
of packets to trigger this behaviour.

Mikkel

On 27 July 2019 at 08.31.52, Kazuho Oku (notifications@github.com) wrote:

However, simply doing that could lead to an amplification attack (as we
know, the amount of data (or packets) the server can send as a reset needs
to be smaller than the amount of data that the server has received).


-- 
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/2844#issuecomment-515664068

v2.23.0 | Report a Bug | By Email