Re: [Webpush] Too strict Crypto-Key restriction imposed by webpush-encryption
Martin Thomson <martin.thomson@gmail.com> Tue, 28 June 2016 23:47 UTC
Return-Path: <martin.thomson@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 ECDA312D8B1 for <webpush@ietfa.amsl.com>; Tue, 28 Jun 2016 16:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
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: 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 hqUcszP0Olug for <webpush@ietfa.amsl.com>; Tue, 28 Jun 2016 16:46:59 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 2EFCF12D8A3 for <webpush@ietf.org>; Tue, 28 Jun 2016 16:46:59 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id w59so16432693qtd.3 for <webpush@ietf.org>; Tue, 28 Jun 2016 16:46:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8ZtyaMkTSn6zhe9Rjk7bADcHtsWcNp+Y07YaaN5DCho=; b=rq+HY43kb52JPvVWk4rKTVPcr7POzK/NXcEoFBmVcBlABqsWLlEBvNMjOu9HtQsGdL f6HFeV8WdWUvvS/KvGeooLCMgDX35K+wR/K8XsaI9vneHpnjJpwqym1sal9OcKUZerW5 XHBq6rri+tP60zOHfxHggWExSzs3+YXv2KlXX7sU8yFaH0lJs+Frss5VlpDn/SmMUs6/ /zEW5xPZ9E9JgT45azFowRGK5uROdlYcQanmgo9sZNHZ2GNEfavWGfXjCIAes52dYK2T IaxaUG99F5w0daHRsWUNQFl1bWTc2AhGoGG+gOmnse/peWDt8784olOIBFwcS+4oXodL nx3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8ZtyaMkTSn6zhe9Rjk7bADcHtsWcNp+Y07YaaN5DCho=; b=gGlBJT1qgA9bMfKjI/W1KF9SODCaOFy20P19aoCQNPHqTqv9srmT64kVhejKsl0Ofa ika9zCBsYed6uzUsjcmK1vPOzNLaYe5s+n5WkUta8NZXWtXtVaC0EK5Kxj8WL1D80p+S YNo7Bu+oZZqxDHUWcGaoHQdmHQxdFQUekLZsbFh5YoDkeybqOPl1S8DAR91/bEBhpMiZ 7MeASS8ZYksDR2pTenHwp25jIrQnuVs/I+h6fGPpBPi9eq3sujE7ykmCdKrsveiSnMVn y3rIValWwHYIpQEUuviePu0MmR4JL/DqBOKrlNslOHhM2CO2meLpmJv5pKtgTCDLga83 kWVw==
X-Gm-Message-State: ALyK8tL+AHrdWRM9wSjHAyv+17uMCu0Z3vAauzDtYB131VBIw+MO+f8u7zSLDBLvIAz3ljMbgVOWK1aiB8OdNQ==
X-Received: by 10.200.44.136 with SMTP id 8mr7543335qtw.18.1467157618290; Tue, 28 Jun 2016 16:46:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.38 with HTTP; Tue, 28 Jun 2016 16:46:57 -0700 (PDT)
In-Reply-To: <CALt3x6ki+vx=cPg1SLR+vkm+Hh-ScQ7vRXKzJMi1WocQNyP=7A@mail.gmail.com>
References: <CALt3x6ki+vx=cPg1SLR+vkm+Hh-ScQ7vRXKzJMi1WocQNyP=7A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 29 Jun 2016 09:46:57 +1000
Message-ID: <CABkgnnVWpakN=E4=X8fdGjuc5F3nWEzbuBWHMumYLiZDy4+DGA@mail.gmail.com>
To: Peter Beverloo <beverloo@google.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/M_QxeEMIl9tCtBI11xVDvbeYNBM>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Too strict Crypto-Key restriction imposed by webpush-encryption
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: Tue, 28 Jun 2016 23:47:01 -0000
On 29 June 2016 at 02:24, Peter Beverloo <beverloo@google.com> wrote: > I've detailed the issue in the following GitHub issue, with an accompanying > pull request relaxing the restriction to a maximum of one Crypto-Key field > having the `dh` parameter: > > https://github.com/webpush-wg/webpush-encryption/issues/6 Which I have merged, since the intent was to limit the number of 'dh' parameters to 1, not to prevent vapid from being used properly..
- Re: [Webpush] Too strict Crypto-Key restriction i… Martin Thomson
- [Webpush] Too strict Crypto-Key restriction impos… Peter Beverloo