Re: [websec] #53: Clarify status of pin validation when used with private trust anchors
"websec issue tracker" <trac+websec@trac.tools.ietf.org> Sat, 25 May 2013 01:41 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 BAFE021F942D for <websec@ietfa.amsl.com>; Fri, 24 May 2013 18:41:17 -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 1bBGiJV1zQSQ for <websec@ietfa.amsl.com>; Fri, 24 May 2013 18:41:17 -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 EF1EF21F9428 for <websec@ietf.org>; Fri, 24 May 2013 18:41:16 -0700 (PDT)
Received: from localhost ([127.0.0.1]:44431 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 1Ug3Tv-0003QI-BE; Sat, 25 May 2013 03:41:15 +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: palmer@google.com
X-Trac-Project: websec
Date: Sat, 25 May 2013 01:41:15 -0000
X-URL: http://tools.ietf.org/websec/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/websec/trac/ticket/53#comment:2
Message-ID: <073.7596c49c42f63bc38fe20a2ed8c59450@trac.tools.ietf.org>
References: <058.27d97f66ed18f6f7f41e08788db76253@trac.tools.ietf.org>
X-Trac-Ticket-ID: 53
In-Reply-To: <058.27d97f66ed18f6f7f41e08788db76253@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: palmer@google.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
Cc: websec@ietf.org
Subject: Re: [websec] #53: Clarify status of pin validation when used with private trust anchors
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: Sat, 25 May 2013 01:41:17 -0000
#53: Clarify status of pin validation when used with private trust anchors Comment (by palmer@google.com): The current draft has this text: 578 <t>If the connection has no errors, then the UA will determine whether to 579 apply a new, additional correctness check: Pin Validation. A UA SHOULD 580 perform Pin Validation whenever connecting to a Known Pinned Host, but MAY 581 allow Pin Validation to be disabled for Hosts according to local policy. For 582 example, a UA may disable Pin Validation for Pinned Hosts whose validated 583 certificate chain terminates at a user-defined trust anchor, rather than a 584 trust anchor built-in to the UA. However, if the Pinned Host Metadata 585 indicates that the Pinned Host is operating in "strict mode" (see 586 <xref target="strict"/>), then the UA MUST perform Pin Validation.</t> I believe this is the result of previous consensus. Is that correct, and can I therefore close this issue? -- -------------------------------+-------------------------------- Reporter: palmer@google.com | Owner: palmer@google.com Type: defect | Status: assigned Priority: major | Milestone: Component: key-pinning | Version: Severity: - | Resolution: Keywords: | -------------------------------+-------------------------------- Ticket URL: <http://tools.ietf.org/wg/websec/trac/ticket/53#comment:2> websec <http://tools.ietf.org/websec/>
- [websec] #53: Clarify status of pin validation wh… websec issue tracker
- Re: [websec] #53: Clarify status of pin validatio… websec issue tracker
- Re: [websec] #53: Clarify status of pin validatio… websec issue tracker
- Re: [websec] #53: Clarify status of pin validatio… Tobias Gondrom
- Re: [websec] #53: Clarify status of pin validatio… Yoav Nir
- Re: [websec] #53: Clarify status of pin validatio… Chris Palmer
- Re: [websec] #53: Clarify status of pin validatio… websec issue tracker