IETF Logo Mail Archive

Re: [quicwg/base-drafts] Preventing KEY_PHASE bit from being used as a tool to correlate CIDs (#1322)

Martin Thomson <notifications@github.com> Mon, 07 May 2018 00:45 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 2397212D87F for <quic-issues@ietfa.amsl.com>; Sun, 6 May 2018 17:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Level:
X-Spam-Status: No, score=-1.606 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 xYJa0wU3Lcr4 for <quic-issues@ietfa.amsl.com>; Sun, 6 May 2018 17:45:36 -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 322FD1267BB for <quic-issues@ietf.org>; Sun, 6 May 2018 17:45:36 -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=gOFlmEtjpmde+uBfVF/pnQEXdvY=; b=R90nbU+pG8uxxLDL CoI292HJEXwZNTZU3f+T4el8Wod33DRB6CkUtC7d1QJOWOqk9P+itscI8739VfU4 F/N2JX+Sxv4hSF6xzfGp5O33iFCX/AC4w/CsK+wuMp3a+VMX3l6X/3p5rQvuxzBC 1lW/IGErdZSycXqULAv4e8QsJFc=
Received: by filter0426p1iad2.sendgrid.net with SMTP id filter0426p1iad2-6970-5AEFA1AE-15 2018-05-07 00:45:34.791832425 +0000 UTC
Received: from github-lowworker-cbd19a4.cp1-iad.github.net (unknown [192.30.252.35]) by ismtpd0019p1iad2.sendgrid.net (SG) with ESMTP id gjkxTp7GRwCnIHA8pPYAEA for <quic-issues@ietf.org>; Mon, 07 May 2018 00:45:34.689 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-cbd19a4.cp1-iad.github.net (Postfix) with ESMTP id BDEEE5809D9 for <quic-issues@ietf.org>; Sun, 6 May 2018 17:45:34 -0700 (PDT)
Date: Mon, 07 May 2018 00:45:35 +0000
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5b607337894dccf7de28f38bc17331dbca65c26a92cf00000001170763ae92a169ce12e69628@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1322/386929936@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1322@github.com>
References: <quicwg/base-drafts/issues/1322@github.com>
Subject: Re: [quicwg/base-drafts] Preventing KEY_PHASE bit from being used as a tool to correlate CIDs (#1322)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aefa1aebbfb8_125f03ff5be018f80157180"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
categories: subscribed
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1tzn42Ps88zr64+c1eZh8ULPLOEgW7gK5xty 4Q1Ulpjb6+VTYb8gnjKaZaOpVTH2do7kS3qzbfbxfOcur3SbsmYk0LjnfiTSTQzQcrE7LBjPUiZhoc b+6Rzn922dxbzhpm7eR7/AYcq80e94SYfkeCUje7RsUN0+//NKEvRFiQxwRovwnspIBAFIrt9D0hEL A=
X-SG-ID: A4fhEY3diXC81rW45KdZlyZUeIsAZbh4s7lWAZfiJNE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/oTRk3Y_CFHj-jkdM-O4o-i-VBM8>
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: Mon, 07 May 2018 00:45:38 -0000

I think that all of this is too complicated.  Here's a simple solution for this issue:

NEW_CONNECTION_ID can carry an extra hard-to-guess bit that masks the KEY_PHASE bit so that it can't be used to correlate flows.

We also recommend that endpoints that don't use connection IDs can randomly do a key update when they migrate to a new path to break linkability.  That creates uncertainty about which half of the population they are correlated with.

-- 
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/1322#issuecomment-386929936

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