IETF Logo Mail Archive

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

Yaron Sheffer <yaronf.ietf@gmail.com> Sun, 15 May 2016 17:10 UTC

Return-Path: <yaronf.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 6E65412D1E6 for <websec@ietfa.amsl.com>; Sun, 15 May 2016 10:10:22 -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 MYglaHEf_YU5 for <websec@ietfa.amsl.com>; Sun, 15 May 2016 10:10:21 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 2D0F712D1E4 for <websec@ietf.org>; Sun, 15 May 2016 10:10:21 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id x201so238645818oif.3 for <websec@ietf.org>; Sun, 15 May 2016 10:10:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=XRHssBVmQCeuUr/YlLGqqKnHdB6gnTMsRqKLckntROA=; b=bKM5WwdFbq16kJNxdcHGfO606ESZp7q5ut7PY6Hv+n0KgotxYZwPG59fH9haxIql/7 2A0kA9M0UV9Euu7TARCrlG0LI3PxiRRS6vqswq3vrc468tfXknLp0T+VL6P94n11vxSL 8sumQmyjNQYtmjZHrV7PlLvIODWOoOxC3b7SzngSqn0pewi0tqIh1nvUiDZXh7a9uMcA SEWG4a5WGIAL++KPPqb9+hZvoZmtXP3Mw/lxkINyDuvNh2IUwLuUuGJUMTdd+rbza7uH JdmKq3tc/DULQUfNVEKIrjP5MUJ7/iI9rUOCpOZVYiQJMJ7AuCLYPOEDyIT6vquQeJXO PTYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=XRHssBVmQCeuUr/YlLGqqKnHdB6gnTMsRqKLckntROA=; b=NqVNPyT2s1UYZmoH628UouDc5onu30JOAS+RBNtK2HXhBspnGsnsP/zocK8iOpOX2l aSXGjJxIlZGxlsdrth+tQ9Nh1YyYaHxnIFnwlqLCis5m+lSe94XPUTm659ghAljVfGJP Ny+N+7HHhiuGy+r65mE25EziZrzCnuou/pLYegNqoqkK1VQIYJRggw49+fr7KVwkVG4o Lc8Rj4Ccs4WaUi9d/AiUDr6bmOpPWsk26uL9QJgyJ0eKe01uoNBtw+pjKU3KFNSk5Ipa yMlHKpYIoTnoQcfLIwUZ4J5Ds9Fp4mYSGJjKYFJiKGcBDmablsitcQJ9MqPH7NnDksOm sVyg==
X-Gm-Message-State: AOPr4FXMwAd1NxuIA0xrJgVOz09ORLzbeRWf4E6BRTQYvfmlyxgcIWljCWko0lFTRxnXcg==
X-Received: by 10.202.218.84 with SMTP id r81mr14999299oig.49.1463332220477; Sun, 15 May 2016 10:10:20 -0700 (PDT)
Received: from [172.18.133.40] (cowboy.intuit.com. [65.204.229.11]) by smtp.gmail.com with ESMTPSA id bb9sm4336430oec.6.2016.05.15.10.10.18 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 15 May 2016 10:10:19 -0700 (PDT)
To: Yoav Nir <ynir.ietf@gmail.com>, Jesse Wilson <jesse@swank.ca>
References: <CAME=j1=QZTFdxaMQ=_Egy296zhAiL--2hcW0_nc-3BLgz7z9XA@mail.gmail.com> <2133CA94-B702-4A6C-BB79-01B773762168@gmail.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <5738AD77.6060509@gmail.com>
Date: Sun, 15 May 2016 20:10:15 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <2133CA94-B702-4A6C-BB79-01B773762168@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/websec/TgIv84ZuyCiwZt-Oxk0dEUD7Q-c>
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 17:10:22 -0000


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?

Thanks,
     Yaron

v2.23.0 | Report a Bug | By Email