[websec] #53: Clarify status of pin validation when used with private trust anchors
"websec issue tracker" <trac+websec@trac.tools.ietf.org> Mon, 15 October 2012 23:09 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 BFA6821F88A0 for <websec@ietfa.amsl.com>; Mon, 15 Oct 2012 16:09:14 -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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMB-4Rv7KQpK for <websec@ietfa.amsl.com>; Mon, 15 Oct 2012 16:09:13 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id 5A14B21F889C for <websec@ietf.org>; Mon, 15 Oct 2012 16:09:13 -0700 (PDT)
Received: from localhost ([127.0.0.1]:34988 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+websec@trac.tools.ietf.org>) id 1TNtmP-0003Uy-8C; Tue, 16 Oct 2012 01:09:01 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: websec issue tracker <trac+websec@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: palmer@google.com
X-Trac-Project: websec
Date: Mon, 15 Oct 2012 23:09:01 -0000
X-URL: http://tools.ietf.org/websec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/websec/trac/ticket/53
Message-ID: <058.27d97f66ed18f6f7f41e08788db76253@trac.tools.ietf.org>
X-Trac-Ticket-ID: 53
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: [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: Mon, 15 Oct 2012 23:09:14 -0000
#53: Clarify status of pin validation when used with private trust anchors Clarify in the I-D whether and how, when a the server's certificate chain chains up to a private trust anchor (as opposed to a publicly-trusted one such as in Mozilla's or Microsoft's root CA programs), the UA should perform pin validation. Options: * If anchor is private, do not perform pin validation * Always perform pin validation, presumably always failing when trust anchor is private * If anchor is private, validate against a database of private pins; ** If there is no DB of private pins, do not perform pin validation ** If there is no DB of private pins, perform pin validation anyway (presumably always failing) * Other options? Currently, Google Chrome opts to not perform pin validation when the trust anchor is private. -- -------------------------+---------------------- Reporter: palmer@… | Owner: palmer@… Type: defect | Status: new Priority: major | Milestone: Component: key-pinning | Version: Severity: - | Keywords: -------------------------+---------------------- Ticket URL: <http://trac.tools.ietf.org/wg/websec/trac/ticket/53> 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