IETF Logo Mail Archive

Re: [websec] HPKP & different encodings of the same public key

Jeffrey Walton <noloader@gmail.com> Sun, 15 May 2016 22:23 UTC

Return-Path: <noloader@gmail.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BEF412D0DF for <websec@ietfa.amsl.com>; Sun, 15 May 2016 15:23:48 -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 zuioUSe1Aywz for <websec@ietfa.amsl.com>; Sun, 15 May 2016 15:23:46 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (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 C850412B054 for <websec@ietf.org>; Sun, 15 May 2016 15:23:46 -0700 (PDT)
Received: by mail-ig0-x22f.google.com with SMTP id m9so31726042ige.1 for <websec@ietf.org>; Sun, 15 May 2016 15:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-transfer-encoding; bh=GhtV2nlrxr8pTyy5ZksDzm1VEMoyeQPvc8ngmgqZLOo=; b=ztgEJh9glbvBcRteyU5aega1+f33LwOEOI/pHhJDlDHRV+859ZOwWsjrjUwuVhM+D7 8lB+v3xEXk7cFO3+GU23PTf6q88xBu9JLT9y+6paHpVIlLKydkAJSAkCXofEEnyTPnUJ 21xRrIsIQza9qejxkfhTTUDtycaXaOXSQZ1U6RRcvth8qFVn84x8mDsOTLh2PZcQ7YMk 5LCxCgUZCKqjRiLOgzo3IXCUKbiSVcjhCZNVg/dJTWLEsQCU3TBUhJv08e25X1DPxv7e D5pOzgwJIMTSwo+JdNdFH0Xgr7mWJ7xi1rC3hanvNxeiob6dvY4ckMWGaIZE/AvMZosi ytHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-transfer-encoding; bh=GhtV2nlrxr8pTyy5ZksDzm1VEMoyeQPvc8ngmgqZLOo=; b=k1sp2XgMnrbHR+sq9o7Ev7rBVHoAMxw28pDaCTwwKAXLNupTg5Why3bTYPOnCs1hLR WyQ90ba0Zx3uEONmfAaYZYI1wxtyQqPjI00wVwVK89ELPlm+BJmXEJRo9OThKuyTIKHb KwH7FstLp2hKda6SLuKytBmCVSnyS/YiC0xXEYYoGQk19wC2i9ZzsQqBB+wUjnrsXKJN 21u9jKs11+xBAYvLLNb0Vb+KPIumqMcYuQBIqMO/VZMZDLseZ5shynVQXNsZkphVQCUM E771RN3nvz/NDrtety9tZBWufEKM9S/eY2jezo/JAc8KFdTCGZFBx1wg62+7WsDrl0Dn gVYg==
X-Gm-Message-State: AOPr4FVliKQWnGjTvoisHIS1assJuZzOCfdNSjmjQcBNCzZDvqYkOF0AgFUQ+iQvz6onGAo6+3QKkHs7D9BwyQ==
MIME-Version: 1.0
X-Received: by 10.50.20.10 with SMTP id j10mr6673754ige.30.1463351026195; Sun, 15 May 2016 15:23:46 -0700 (PDT)
Received: by 10.64.126.67 with HTTP; Sun, 15 May 2016 15:23:46 -0700 (PDT)
In-Reply-To: <CAME=j1=PimfS=rA3MBAY_8YwsvYzg1x8+FvkgzMEw-qBR9PTyw@mail.gmail.com>
References: <CAME=j1=QZTFdxaMQ=_Egy296zhAiL--2hcW0_nc-3BLgz7z9XA@mail.gmail.com> <CAFewVt7u2e6184T_XP7VFJRbz4XJyrxUf2VK8XtZg3FQCquZ3g@mail.gmail.com> <CAME=j1=PimfS=rA3MBAY_8YwsvYzg1x8+FvkgzMEw-qBR9PTyw@mail.gmail.com>
Date: Sun, 15 May 2016 18:23:46 -0400
Message-ID: <CAH8yC8kuaBsmjJy673k+qYfo-_BbEQZFmLKGSYGQ11MMT+6LfQ@mail.gmail.com>
From: Jeffrey Walton <noloader@gmail.com>
To: Jesse Wilson <jesse@swank.ca>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/websec/NXZi3FLH1t-pdWB4WmImXjLGQyk>
Cc: IETF WebSec WG <websec@ietf.org>
Subject: Re: [websec] HPKP & different encodings of the same public key
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: noloader@gmail.com
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/websec/>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2016 22:23:48 -0000

On Sun, May 15, 2016 at 5:19 PM, Jesse Wilson <jesse@swank.ca> wrote:
> Thanks Brian! I’m happy to hear that this is an implementation bug (that I
> can petition to get fixed), rather than spec bug (that we all have to
> workaround).

It depends on the issuing policies.

The IETF has no way to specify that a certificate was created or
issued under PKIX, so its a moot point. (It creates a vaccum like the
EV mess, except for standard certificates rather than EV
certificates).

Jeff

v2.23.0 | Report a Bug | By Email