Re: [Webpush] CALL FOR CONSENSUS: VAPID cut-and-paste protection

Martin Thomson <> Fri, 18 August 2017 04:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1DBAF132836 for <>; Thu, 17 Aug 2017 21:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 EYWjkvGfLfg2 for <>; Thu, 17 Aug 2017 21:16:58 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 420E01323BD for <>; Thu, 17 Aug 2017 21:16:58 -0700 (PDT)
Received: by with SMTP id m88so29408500iod.2 for <>; Thu, 17 Aug 2017 21:16:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uvooI3DQUyd9DsDvsl878iYpb6LG4hkcJK9jofzVYYk=; b=rrcafx0pYXYstbpsk9nEkDI1aqyLJPZhd2xtmCc9UrOp+3kgABn5jKfJ/7ocU090vp 52by1spVy5Z/SQs8nkPq4KTyCsjPxVxWCAGYrthW5BKHPcT93Oa1QUp6tuT7eQ5526RL UqLJcv7x7s35N9taOHciQhwCJ9JIe/0gJDeJGoEwoAi6dlb5PaaILfM3r6qrRckELQ5o xyptEvj1Z0DGOJc67sWG5JLyz++jtB85C78zzOjyB/BuQgTWF5bPhX9oO6IXbTq8c50d O71P2BkVEmoK+qNnXjLN7aOtTsKpxT9e/ni4fNqbefatLLHPC9P4HV+aJRagMoutKngh XmHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uvooI3DQUyd9DsDvsl878iYpb6LG4hkcJK9jofzVYYk=; b=oq0SHoIIO3DdrjzGMcKdXMDy5bjhKCg22LBl01lu0RZIZBXpw4HbsXE5rWOJLZ3N9C UeVhSsh7ldeyrDLmt9uZ3naA2BlMc+7jasuYpWqyS1ycmcOP57SMY+xfSAjAUohR8TqV 90iP/ez3Leh3YJ0BddTwZtQLQulYvaK8L4I0TLvecYhJEpSw7OZBrSamte4Ai2QeXO/s shzvbCkE4yREMi8hSNVJfkS/o7TQME1B0ub9/hL+oVT44LpmPhTTTMuTDCWHgoQWQrc+ SwXZwEmN2sT0CVs/u3Gc7MVHUTGyK8tWl3G06Vd2xhNk9YeSmY2HwzuDNsKqXlryN/rQ C3MA==
X-Gm-Message-State: AHYfb5gWl2POmBnxA4bfwFBexxyEOe24sA+DS5CwSUr+PhnA6SzkM3Fq qnc0F2KGz+JxW9RY1yfJsdd7DA1+6w==
X-Received: by with SMTP id z62mr7716282iof.74.1503029817565; Thu, 17 Aug 2017 21:16:57 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 17 Aug 2017 21:16:57 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Martin Thomson <>
Date: Fri, 18 Aug 2017 14:16:57 +1000
Message-ID: <>
To: Phil Sorber <>
Cc: "" <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Webpush] CALL FOR CONSENSUS: VAPID cut-and-paste protection
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 18 Aug 2017 04:17:00 -0000

On 18 August 2017 at 12:58, Phil Sorber <> wrote:
> I believe the working group has already discussed adding such a mechanism
> and rejected it (with citation to an email discussion or minutes reflecting
> such discussion).

We did consider options that don't have this unfortunate property.
Client certificates were a strong contender.  They would have been
ideal if not for operational challenges.

Here's the email that I think was pivotal on this subject:

Later there is also:

There are yet more emails that follow on from this where we discuss
scope of the token and relative costs.  The first of those is here:

I found the rest of thread instructive as a reminder of what happened,
I had forgotten the details of this discussion.

I didn't read meeting minutes, the above seems sufficient.