[websec] #58: Should we pin only SPKI, or also names

"websec issue tracker" <trac+websec@trac.tools.ietf.org> Mon, 29 July 2013 15:11 UTC

Return-Path: <trac+websec@trac.tools.ietf.org>
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 85D9B21F99CF for <websec@ietfa.amsl.com>; Mon, 29 Jul 2013 08:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13A+jcOEP+Pt for <websec@ietfa.amsl.com>; Mon, 29 Jul 2013 08:11:37 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 9DAD011E80EE for <websec@ietf.org>; Mon, 29 Jul 2013 08:10:41 -0700 (PDT)
Received: from localhost ([127.0.0.1]:40882 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+websec@trac.tools.ietf.org>) id 1V3p56-0007o3-AH; Mon, 29 Jul 2013 17:09:52 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "websec issue tracker" <trac+websec@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-websec-key-pinning@tools.ietf.org, ynir@checkpoint.com
X-Trac-Project: websec
Date: Mon, 29 Jul 2013 15:09:52 -0000
X-URL: http://tools.ietf.org/websec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/websec/trac/ticket/58
Message-ID: <060.be9b0009dc0350ca543f553042673944@trac.tools.ietf.org>
X-Trac-Ticket-ID: 58
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-websec-key-pinning@tools.ietf.org, ynir@checkpoint.com, websec@ietf.org
X-SA-Exim-Mail-From: trac+websec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: cevans@google.com, palmer@google.com, sleevi@google.com
Resent-Message-Id: <20130729151103.9DAD011E80EE@ietfa.amsl.com>
Resent-Date: Mon, 29 Jul 2013 08:10:41 -0700 (PDT)
Resent-From: trac+websec@trac.tools.ietf.org
Cc: websec@ietf.org
Subject: [websec] #58: Should we pin only SPKI, or also names
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 29 Jul 2013 15:11:39 -0000

#58: Should we pin only SPKI, or also names

 It has been suggested that instead or in addition to pinning to a has of
 the SPKI, we should also be able to pin to a certificate vendor. So in
 addition to the current pins, like

    Public-Key-Pins: max-age=2592000;
        pin-sha1="4n972HfV354KP560yw4uqe/baXc=";
        pin-sha256="LPJNul+wow4m6DsqxbninhsWHlwfp0JecwQzYpOLmCQ="

 We will also be able to specify something like this:

    Public-Key-Pins: max-age=2592000;
        pin-name="comodo"

-- 
-------------------------+-------------------------------------------------
 Reporter:               |      Owner:  draft-ietf-websec-key-
  ynir@checkpoint.com    |  pinning@tools.ietf.org
     Type:  enhancement  |     Status:  new
 Priority:  major        |  Milestone:
Component:  key-pinning  |    Version:
 Severity:  In WG Last   |   Keywords:  HPKP
  Call                   |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/websec/trac/ticket/58>
websec <http://tools.ietf.org/websec/>