datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

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

Document type: Active Internet-Draft (websec WG)
Document stream: IETF
Last updated: 2014-02-07
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Web Security                                                    C. Evans
Internet-Draft                                                 C. Palmer
Intended status: Standards Track                               R. Sleevi
Expires: August 12, 2014                                    Google, Inc.
                                                        February 8, 2014

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

Abstract

   This memo describes an extension to the HTTP protocol allowing web
   host operators to instruct user agents (UAs) to remember ("pin") the
   hosts' cryptographic identities for a given period of time.  During
   that time, UAs will require that the host present 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 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 August 12, 2014.

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 August 12, 2014                [Page 1]
Internet-Draft    Public Key Pinning Extension for HTTP    February 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 . . . . . . . . . . . . . . . . . .   3
   2.  Server and Client Behavior  . . . . . . . . . . . . . . . . .   3
     2.1.  Response Header Field Syntax  . . . . . . . . . . . . . .   3
       2.1.1.  The max-age Directive . . . . . . . . . . . . . . . .   5
       2.1.2.  The includeSubDomains Directive . . . . . . . . . . .   5
       2.1.3.  The report-uri Directive  . . . . . . . . . . . . . .   5
       2.1.4.  Examples  . . . . . . . . . . . . . . . . . . . . . .   6
     2.2.  Server Processing Model . . . . . . . . . . . . . . . . .   7
       2.2.1.  HTTP-over-Secure-Transport Request Type . . . . . . .   7
       2.2.2.  HTTP Request Type . . . . . . . . . . . . . . . . . .   8
     2.3.  User Agent Processing Model . . . . . . . . . . . . . . .   8
       2.3.1.  Public-Key-Pins Response Header Field Processing  . .   8
       2.3.2.  Noting a Pinned Host - Storage Model  . . . . . . . .   9
       2.3.3.  HTTP-Equiv <Meta> Element Attribute . . . . . . . . .  10
     2.4.  Semantics of Pins . . . . . . . . . . . . . . . . . . . .  10
     2.5.  Noting Pins . . . . . . . . . . . . . . . . . . . . . . .  11
     2.6.  Validating Pinned Connections . . . . . . . . . . . . . .  12
     2.7.  Interactions With Preloaded Pin Lists . . . . . . . . . .  12
     2.8.  Pinning Self-Signed End Entities  . . . . . . . . . . . .  13
   3.  Reporting Pin Validation Failure  . . . . . . . . . . . . . .  13
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
     4.1.  Maximum max-age . . . . . . . . . . . . . . . . . . . . .  17
     4.2.  Using includeSubDomains Safely  . . . . . . . . . . . . .  17
     4.3.  Backup Pins . . . . . . . . . . . . . . . . . . . . . . .  18
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  19
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   7.  Usability Considerations  . . . . . . . . . . . . . . . . . .  20
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  20

[include full document text]