IETF Logo Mail Archive

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

Yoav Nir <ynir.ietf@gmail.com> Sun, 15 May 2016 18:26 UTC

Return-Path: <ynir.ietf@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 E065D12D18A for <websec@ietfa.amsl.com>; Sun, 15 May 2016 11:26:02 -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 idDFNHioNMip for <websec@ietfa.amsl.com>; Sun, 15 May 2016 11:26:02 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 ADA9F12D0AF for <websec@ietf.org>; Sun, 15 May 2016 11:26:01 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id a17so104635604wme.0 for <websec@ietf.org>; Sun, 15 May 2016 11:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=uOxFXdNhYvhJFIr75C1/WlCx0MSPJFJAwUpdtiuKRiU=; b=0t3Q4Dd/Gcv8teoyS0ljH8xcFs7jBVDf22w+vkPbZ7fOwvNjueTFycjyEh80iF/FFl waCBLQRP0pJiLIld7K+KeOQxR54nvciSL9bKTFBzfezpBV7pmayI4Lb+JNBokikU6kU3 3ISxgCkjai5m+JmItb9y1gTt/04tvO+ywSjVrgPvHGVP8SfJBdxeR9iHlnZonE/WIk/Q 9u/ZIma/F0GWiMik7eHREiaCcDay9f0la+L2bd6pwLBk/7mhPagSPH4+MZ94PZi7kc/5 Vr86+z3p7JNjNyrHktcW7O+ShO3DDM1GgmYC93vVHprxeodexlJhXCoZtNy7c+OnROyz y4dQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=uOxFXdNhYvhJFIr75C1/WlCx0MSPJFJAwUpdtiuKRiU=; b=ZejdVf7Y9Ansaneuk0mIXE4etdo120XYAvKW3hl2ZUbxZ2GyEhEiMQ++PzGJgk5sYL dZG5vGezV1UvFRz1M1fgjxUFv9DcGwwWUR4ZK2vC+ZT8Vfz1ls8GJFQe6Mqb8b/9VTNC bca0Z3m2G4jsjftc6F5P31CRlNJcl6Ji1BTODhco7tq7qia/N6xjznASX9Y+B1JQJ804 z0T4PV1OZz5B9djJq8LKvLZqWFDZgo+1TIQrBv8d3qodaBdTP2e3i8xbb/1rGQxuSoU7 WdbstEkmvQ+rnRzzhquD3TbqY1kRSh4LfmNnSiNIsZx6abksy5lrNu3TNvdeF799y5a0 A1qQ==
X-Gm-Message-State: AOPr4FVMcRmMIp8TL+iQUVukycKurwGIiitaWQ0Jik5chrg7DA1YJ7p+A1Ay9zd22w+YpA==
X-Received: by 10.28.227.138 with SMTP id a132mr13324577wmh.35.1463336760289; Sun, 15 May 2016 11:26:00 -0700 (PDT)
Received: from [192.168.1.12] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id i194sm14315023wmf.6.2016.05.15.11.25.58 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 15 May 2016 11:25:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <5738AD77.6060509@gmail.com>
Date: Sun, 15 May 2016 21:24:26 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB5F3822-264B-4570-B5B4-39E0DB914358@gmail.com>
References: <CAME=j1=QZTFdxaMQ=_Egy296zhAiL--2hcW0_nc-3BLgz7z9XA@mail.gmail.com> <2133CA94-B702-4A6C-BB79-01B773762168@gmail.com> <5738AD77.6060509@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/websec/0wHYCOVKMt-NrsY7NDsa0xw6jpg>
Cc: 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
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 18:26:03 -0000

> On 15 May 2016, at 8:10 PM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
> 
> 
> 
> On 15/05/16 10:22, Yoav Nir wrote:
>> That’s interesting. With HPKP you can pin keys from existing certificates, or keys that are not (yet) in certificates.
>> 
>> One of the early deployment scenarios (which got de-emphasized later on) was that you include two pins: your current production key and a spare key that you will certify if something bad happens to the production key (like the private key leaking out).
>> 
>> 
> Hi Yoav,
> 
> I had assumed this *is* the main deployment scenario. If it was de-emphasized, what do you consider as the "classic" HPKP usage scenario?

Current certificate plus some CA certificate that you are likely to use to certify your next certificate.

Yoav

v2.23.0 | Report a Bug | By Email