Public Key Pinning Extension for HTTP
draft-ietf-websec-key-pinning-21

 
Document
Type Active Internet-Draft (websec WG)
Last updated 2014-10-14 (latest revision 2014-10-05)
Replaces draft-evans-palmer-key-pinning
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream
WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Yoav Nir
Shepherd write-up Show (last changed 2014-06-25)
IESG
IESG state RFC Ed Queue
Telechat date
Responsible AD Barry Leiba
Send notices to websec-chairs@ietf.org, draft-ietf-websec-key-pinning@ietf.org
IANA
IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack

Email authors IPR References Referenced by Nits Search lists

Web Security                                                    C. Evans
Internet-Draft                                                 C. Palmer
Intended status: Standards Track                               R. Sleevi
Expires: April 8, 2015                                      Google, Inc.
                                                         October 5, 2014

                 Public Key Pinning Extension for HTTP
                    draft-ietf-websec-key-pinning-21

Abstract

   This document defines a new HTTP header that allows web host
   operators to instruct user agents to remember ("pin") the hosts'
   cryptographic identities over a period of time.  During that time,
   UAs will require that the host presents a certificate chain including
   at least one Subject Public Key Info structure whose fingerprint
   matches one of the pinned fingerprints for that host.  By effectively
   reducing the number of trusted authorities who can authenticate the
   domain during the lifetime of the pin, pinning may reduce the
   incidence of man-in-the-middle attacks due to compromised
   Certification Authorities.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 8, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Evans, et al.             Expires April 8, 2015                 [Page 1]
Internet-Draft    Public Key Pinning Extension for HTTP     October 2014

   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Server and Client Behavior  . . . . . . . . . . . . . . . . .   4
     2.1.  Response Header Field Syntax  . . . . . . . . . . . . . .   4
       2.1.1.  The pin- Directive  . . . . . . . . . . . . . . . . .   5
       2.1.2.  The max-age Directive . . . . . . . . . . . . . . . .   6
       2.1.3.  The includeSubDomains Directive . . . . . . . . . . .   6
       2.1.4.  The report-uri Directive  . . . . . . . . . . . . . .   6
       2.1.5.  Examples  . . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Server Processing Model . . . . . . . . . . . . . . . . .   8
       2.2.1.  HTTP-over-Secure-Transport Request Type . . . . . . .   8
       2.2.2.  HTTP Request Type . . . . . . . . . . . . . . . . . .   9
     2.3.  User Agent Processing Model . . . . . . . . . . . . . . .   9
       2.3.1.  Public-Key-Pins Response Header Field Processing  . .   9
       2.3.2.  Interaction of Public-Key-Pins and Public-Key-Pins-
               Report-Only . . . . . . . . . . . . . . . . . . . . .  10
       2.3.3.  Noting a Pinned Host - Storage Model  . . . . . . . .  11
       2.3.4.  HTTP-Equiv <Meta> Element Attribute . . . . . . . . .  12
     2.4.  Semantics of Pins . . . . . . . . . . . . . . . . . . . .  12
     2.5.  Noting Pins . . . . . . . . . . . . . . . . . . . . . . .  13
     2.6.  Validating Pinned Connections . . . . . . . . . . . . . .  14
     2.7.  Interactions With Preloaded Pin Lists . . . . . . . . . .  15
     2.8.  Pinning Self-Signed End Entities  . . . . . . . . . . . .  15
   3.  Reporting Pin Validation Failure  . . . . . . . . . . . . . .  15
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
     4.1.  Maximum max-age . . . . . . . . . . . . . . . . . . . . .  19
     4.2.  Using includeSubDomains Safely  . . . . . . . . . . . . .  19
     4.3.  Backup Pins . . . . . . . . . . . . . . . . . . . . . . .  20
     4.4.  Interactions With Cookie Scoping  . . . . . . . . . . . .  21
Show full document text