IETF Logo Mail Archive

Re: [Webpush] Vapid public key

Costin Manolache <costin@gmail.com> Wed, 02 November 2016 20:22 UTC

Return-Path: <costin@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA76129489 for <webpush@ietfa.amsl.com>; Wed, 2 Nov 2016 13:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 4lbaBWVBExOr for <webpush@ietfa.amsl.com>; Wed, 2 Nov 2016 13:22:53 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 E134A1298C7 for <webpush@ietf.org>; Wed, 2 Nov 2016 13:22:51 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id 62so36225001oif.1 for <webpush@ietf.org>; Wed, 02 Nov 2016 13:22:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=573MBszHyo/zR5vvYwPe52bAcp7sb5b8aOYFjzFpaKY=; b=IlTDHGIfEkJ+zRsUpCoeCNGMhuXTAi2Qnb05syQ+LNR2ZtMJ3xUKa5682irr03vohL m5h/NCxh2WOHlBxN3xl46MnsRXd7l96tNDQGfw9NLMxw51dPGNxDTMTbgcWie5ujNrLw om96FsyMXNjeirnUNYGwkpmrWqAtj1LdOC9+lcE4p6hGGUse1BkQmBX9tjPU8pzXlvKk nwjvnguUHH2S2obic1THsCAxDAEKIYyGW6NY19kePoX3msKZ5zwr87tdNyIlMU6Pua2g 4wiY8IcAtKDG1II6nr7KX3AfycGfZXu2T9QDTTdbL2ZGRHqKrMzOa7qDF+0pq6AS2RMx yQ3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=573MBszHyo/zR5vvYwPe52bAcp7sb5b8aOYFjzFpaKY=; b=exDcgVRC8+l8h4ajnGmEdNlimQzsycSUahFj2T8lnNgTXor1gZyCfThiMQuF6jaLfx 7IZKcHB8Dzz3JXQfHq9WEIeQzni13dsEr+aRoXLvgK9PKDM307M4Nd+/WN/nnHXBANuR yq9jVO8sN+tV/LOrziO0fDsqdu5OsOwI6+92h6LkcFlwrrQrE3yT5lanmlMltMZAslMq BA0Y42sj+9L1RMY2udmy3sYJqMWN6g8jZjGAPhQb6KjJiAYlleWPLoGRWykWsycdYaAe oz0J3KwcxdJ4PARBnSiv2OoATdRVDvjJZqSRKUx4Ik1v28dMlHgavdxb8LU64i/jyYMD 5dkQ==
X-Gm-Message-State: ABUngvfQ4ru1v312m96m+dT4JtWptVwESLNfirORcAdRbjIEfJm4kTzBpaLeMzUOGSNOAPntzw09ohM9ihBM7A==
X-Received: by 10.107.2.8 with SMTP id 8mr2557908ioc.83.1478118171183; Wed, 02 Nov 2016 13:22:51 -0700 (PDT)
MIME-Version: 1.0
References: <CABkgnnVKd+kAZPD5KirF7NaGMDBSpaO6FR3yE8d+c3ge3-He3w@mail.gmail.com> <CAP8-FqmBUHd5up7Jfo+veFWvL22XiPwGGXNnOW6rm7nxeESU_g@mail.gmail.com> <CABkgnnX4aAjnZyu3morJOLatuuj9k4NSoTpoNtF7YjtRUFQOnQ@mail.gmail.com> <CAP8-Fq=Zd66ZhWm+gYesOpc2NZ-YBpy2+bHdr6O+h1KG2s16uw@mail.gmail.com> <CAP8-FqkfjQkm-z9HSBHMm3nht8SFBY5G=W82N8BAybbxucdEag@mail.gmail.com> <4538eada-c406-fa72-fec1-1c26bb225a1f@mozilla.com>
In-Reply-To: <4538eada-c406-fa72-fec1-1c26bb225a1f@mozilla.com>
From: Costin Manolache <costin@gmail.com>
Date: Wed, 02 Nov 2016 20:22:40 +0000
Message-ID: <CAP8-FqkhniWyD9UDxbV3nh=d04A=otMzOPHTOxac=edjzYpVww@mail.gmail.com>
To: jr conlin <jconlin@mozilla.com>, Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="001a1139787687946f054057345b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/N7PcJwiXokrxDUKLBbq1hyQ8f4A>
Cc: "webpush@ietf.org" <webpush@ietf.org>, Peter Beverloo <beverloo@google.com>
Subject: Re: [Webpush] Vapid public key
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol <webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>, <mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>, <mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2016 20:22:56 -0000

Apologies for any bad memories related to implementing digest auth :-)

If we are updating the vapid spec - I would like to ask for one more change:

"A UA may also authenticate with VAPID when making a subscribe request. If
subscribe was
authenticated with VAPID, all subsequent subscribe, unsubscribe, ack or
monitor requests
associated with the same pushset MUST be authenticated with VAPID with same
public key"

I know subscribe/monitor are over SSL - but I think it improves a bit the
security, and the device
already needs to have code to handle EC for the e2e encryption. The main
concern is
an attacker 'acking' or unsubscribing - since the messages are e2e
encrypted they can't read it.

Costin

On Wed, Nov 2, 2016 at 12:43 PM jr conlin <jconlin@mozilla.com> wrote:

> On 11/2/2016 11:14 AM, Costin Manolache wrote:
>
> From rfc2617 (digest auth):
>
> Authorization: Digest username="Mufasa",
>                  realm="testrealm@host.com",
>                  nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093",
>                  uri="/dir/index.html",
>                  qop=auth,
>                  nc=00000001,
>                  cnonce="0a4f113b",
>                  response="6629fae49393a05397450978507c4ef1",
>                  opaque="5ccc069c403ebaf9f0171e9517f40e41"
>
> No "favoriteDrink"?
>
> /me fights back his x.500 PTSD.
>
>

v2.23.0 | Report a Bug | By Email