Re: [Masque] MASQUE detection through tracking trackers

Töma Gavrichenkov <> Tue, 05 November 2019 17:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DABA21200C4 for <>; Tue, 5 Nov 2019 09:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id F6RjqWMm8M0c for <>; Tue, 5 Nov 2019 09:31:48 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::b32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CCC8912001A for <>; Tue, 5 Nov 2019 09:31:48 -0800 (PST)
Received: by with SMTP id 4so9691920ybq.9 for <>; Tue, 05 Nov 2019 09:31:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c4O2txnJ9qKS+H7dDr2cDD7TGbCKIqZRX7+Nvlc50hY=; b=q/XK0hH5+7nl3Yf1yZq5feAlcKtJzRLsyOd8u6B168T0jfSd2FrD4AMrcuGtzc70bV LFqXdlfHGECvlQMooSoOUf7IiXsLYs7SNpV5qMIMW77fdP8Cv5EduaDpWnMFVEjYgz2k 00JaPRF8wawn1or7KcVihmgUfBQ9zqkT2O4Bgn8mseQFAzqTQKsRGG27gR2ziclK+7J/ 9UIg7GT2TEhQMGc9ErucMVKERlbKkPE3C3efeQ+QaTfeY9M1tHzXp1fKfus9dF+nY2a2 cYJr8491BMXRsou/mQLyIKACQELVPACOR4y4aNVmo6RWwUpgnbK3VBHyE2vK3wDaplML d5aA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c4O2txnJ9qKS+H7dDr2cDD7TGbCKIqZRX7+Nvlc50hY=; b=KbL/Ot78z+6x3ovpbjWs1fa0aF0++UfDRt3yb2ZnYPpbz977qjP5r8Jxe0eK523RE4 KGOPbJYySCg+MDnNjnm9qYjhxqzfvNnG7LtjKJwrhM1Qho9l8TOnCWAiX+woShuY/c8z NuUxdK6rBicfvQXBRjYX9wvqbmv8NK7REhZSVa7Mx0vnu6V4NsKZHavOT2FztL4e4gqI uGzY77GQpcDEjX5zS78iyxuVE4OIA3KBLmeLf3Jidl0MsDTB0jybiiX6LcD9nuAhsW9f mTEF8pps4y2rVjR9ryWWGUOAoQb7I0VV7UCELIafhujeUU1cq/3fZw2LEr9D94YHdPWW qEmQ==
X-Gm-Message-State: APjAAAXggelMj1/tq5A8NuaTc7kReb79W7A7h9jvKdYJIvtZC+sKQFw8 0FDTfc6872i7HdKL1Ydzvhna/sHW+GO4CSPlrno=
X-Google-Smtp-Source: APXvYqyd/esXE0M5e46LDMwAmxoR/HCMI7zkDg8j+562xDSMCyS/CXDdSBaUYiY6fELwdlXfn5CleQBSO7Gzr7P3OfI=
X-Received: by 2002:a25:a148:: with SMTP id z66mr30131349ybh.475.1572975107327; Tue, 05 Nov 2019 09:31:47 -0800 (PST)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: =?UTF-8?Q?T=C3=B6ma_Gavrichenkov?= <>
Date: Tue, 5 Nov 2019 20:31:33 +0300
Message-ID: <>
To: Ted Hardie <>
Content-Type: multipart/alternative; boundary="000000000000834d8505969cce03"
Archived-At: <>
Subject: Re: [Masque] MASQUE detection through tracking trackers
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiplexed Application Substrate over QUIC Encryption <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 05 Nov 2019 17:31:51 -0000


On Tue, Nov 5, 2019, 8:15 PM Ted Hardie <> wrote:

> You included HTTP(S) in the "redirect to a web page" here, but it's not
> clear why the client connection would continue far enough to display a web
> page

No, obviously, this is a captive portal story.  Every page would just
display a TLS error, so the user would have to click through it at some
point to regain access.

>> Any idea if this is being sold/deployed in Europe?  Because it looks like
> it amounts to "you must disclose your data to 3rd party trackers" to access
> unrelated resources.

I can't say I'm following your point.

Anyhow, the customer base is mostly out of the EU I believe.  Why?

 I'm hardly a GDPR expert

Me too, but I don't see any issues with GDPR.  The vendor does not own a
Web tracker, they only track existing ones.

> From section 7.1:

Yup, have read it.  PADDING frames won't help here.  A tracker may even not
be running over QUIC.  I, for one, have no idea when e.g. NewRelic is going
to adopt it.