[websec] [Technical Errata Reported] RFC7469 (4354)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 05 May 2015 06:02 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E78A1B2E57 for <websec@ietfa.amsl.com>; Mon, 4 May 2015 23:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 8hQgspca6Z_V for <websec@ietfa.amsl.com>; Mon, 4 May 2015 23:02:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id D336C1B2E46 for <websec@ietf.org>; Mon, 4 May 2015 23:02:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DDA0B180092; Mon, 4 May 2015 23:01:01 -0700 (PDT)
To: cevans@google.com, palmer@google.com, sleevi@google.com, barryleiba@computer.org, tobias.gondrom@gondrom.org, ynir.ietf@gmail.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150505060101.DDA0B180092@rfc-editor.org>
Date: Mon, 04 May 2015 23:01:01 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/websec/nQXYQJQ-0KDRao51LhPxRjCcpNk>
Cc: kirit@felspar.com, websec@ietf.org, rfc-editor@rfc-editor.org
Subject: [websec] [Technical Errata Reported] RFC7469 (4354)
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.15
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: <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: Tue, 05 May 2015 06:02:23 -0000
The following errata report has been submitted for RFC7469, "Public Key Pinning Extension for HTTP". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7469&eid=4354 -------------------------------------- Type: Technical Reported by: Kirit Saelensminde <kirit@felspar.com> Section: 3 Original Text ------------- As in Section 2.4, the token refers to the algorithm name, and the quoted-string refers to the base64 encoding of the SPKI Fingerprint. When formulating the JSON POST body, the UA MUST either use single- quoted JSON strings or use double-quoted JSON strings and backslash- escape the embedded double quotes in the quoted-string part of the known-pin. .... 'pin-sha256="d6qzRu9zOECb90Uez27xWltNsj0e1Md7GkYYkVoZWmM="', Corrected Text -------------- As in Section 2.4, the token refers to the algorithm name, and the quoted-string refers to the base64 encoding of the SPKI Fingerprint. When formulating the JSON POST body, the UA MUST use double-quoted JSON strings and backslash-escape the embedded double quotes in the quoted-string part of the known-pin. .... "pin-sha256=\"d6qzRu9zOECb90Uez27xWltNsj0e1Md7GkYYkVoZWmM=\"", Notes ----- This RFC seems to think that single quotes are permissible in JSON. This is not the case. See http://tools.ietf.org/html/rfc7159#section-7 Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7469 (draft-ietf-websec-key-pinning-21) -------------------------------------- Title : Public Key Pinning Extension for HTTP Publication Date : April 2015 Author(s) : C. Evans, C. Palmer, R. Sleevi Category : PROPOSED STANDARD Source : Web Security Area : Applications Stream : IETF Verifying Party : IESG
- [websec] [Technical Errata Reported] RFC7469 (435… RFC Errata System
- [websec] [Errata Verified] RFC7469 (4354) RFC Errata System