[TLS] ESNI: Tracking and blocking via record_digest
Rob Sayre <sayrer@gmail.com> Mon, 25 November 2019 19:03 UTC
Return-Path: <sayrer@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25870120CB9 for <tls@ietfa.amsl.com>; Mon, 25 Nov 2019 11:03:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 wF2l3Rg2dHKF for <tls@ietfa.amsl.com>; Mon, 25 Nov 2019 11:03:03 -0800 (PST)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 122BF120CB2 for <tls@ietf.org>; Mon, 25 Nov 2019 11:03:02 -0800 (PST)
Received: by mail-io1-xd2a.google.com with SMTP id i11so17441975iol.13 for <tls@ietf.org>; Mon, 25 Nov 2019 11:03:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=RkY6bkTPnvsi/OJlP+IBO44KakaVnLzWa7qkyY2Ojws=; b=MsaM3TDOFkwlSO7X63YxE37PFrhhBq60b7GUN14maqR1WsbhHcpWNj0NsS52HFCh6R tdWB2QzfPsWfTxXAmiecTCcP8cEkabQCQCSdkeu39v6tqQ8QzrTBlGRlyhjcH1+rp7rC //xl028zGy4L9Z/akiUazOvrLcWXhGLio/rbVRZ05OkoujnvEqhiDPog7K6fSOm08FlI gUwKtJa6PvaVBthGsVN3/eCgY24KrnQpP4cUYHX6gV6h8N3iiFaXLL26qoD0DUi1g4Xb zDpkSKaQPLIKrCU/JsPlCHD9T7sYcQqLHiaafJQMygE5HeYiI0s6Rjel9p5J/G8MYtJY vs0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=RkY6bkTPnvsi/OJlP+IBO44KakaVnLzWa7qkyY2Ojws=; b=nsD5upyTAlMmSejqXfvGpBiDSVuSnC6QFmMfGmOTGXu0eSvbKvkNqaB6I5FBXDhwZG /G+yKS8Q/Em24IXeA2OB9L+qCqkSp+B5sCZS79OTUO9IFzMyx2BAOi56ICS6ZxgsHpJ0 9MJGu77SzI0/qmyvmp4ZMiDm3Q/RuEnVMESeCFWtqIiDruxtXBhTHdMZjE1lOsGFijlh HUuFLM53QT2VhNNgJCRrtA/iWfJEyRwue3RwJQMAbjfvYnlLsr9pd5q0K7zhbgBWTcc6 KeFCSWIRLZds4kd4TDV2Q236zWV72JOVXmSFe2CDrGam/tulcReogti6K0KhMy4g3Pcg iOKQ==
X-Gm-Message-State: APjAAAXibRyQlrcnvPvKL2f0cBzmK81PDbjTN1jEFD1x+BVrlzHv3gEH FkeSdmdYj85SWcZGVi6qeDrKvMswH18ESjsRc0X24w==
X-Google-Smtp-Source: APXvYqwTvRMg7+2P9PvJPuModCsXHbJo3BXcu+lhA1Wv3IoKmXvLlruGuEYfTBqE683xO98cAZzVTxB2Br6FV424LBE=
X-Received: by 2002:a5d:9b11:: with SMTP id y17mr11060318ion.73.1574708580804; Mon, 25 Nov 2019 11:03:00 -0800 (PST)
MIME-Version: 1.0
From: Rob Sayre <sayrer@gmail.com>
Date: Mon, 25 Nov 2019 11:02:49 -0800
Message-ID: <CAChr6Sxm3fcZUxm8XwZ-UzvxTMxK8TfyK7JBonz8MG2LMpRGjw@mail.gmail.com>
To: "TLS@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000956e020598306940"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/ScoooPbTWC8zT4oUAqMb1shSV5E>
Subject: [TLS] ESNI: Tracking and blocking via record_digest
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Nov 2019 19:03:05 -0000
Hi, I see the issue of tracking and blocking via record_digest has come up a few times in the github repository, but I don't understand the resolution. If someone wanted to observe or block traffic to "example.com", couldn't they retrieve the ESNI keys, calculate the record_digest themselves, and then use that to spot traffic to "example.com"? Is the idea that DNS providers will vary the shared keys? thanks, Rob
- [TLS] ESNI: Tracking and blocking via record_dige… Rob Sayre
- Re: [TLS] ESNI: Tracking and blocking via record_… Ben Schwartz
- Re: [TLS] ESNI: Tracking and blocking via record_… Rob Sayre
- Re: [TLS] ESNI: Tracking and blocking via record_… Christian Huitema
- Re: [TLS] ESNI: Tracking and blocking via record_… Rob Sayre