Re: [websec] #58: Should we pin only SPKI, or also names

Trevor Perrin <trevp@trevp.net> Sun, 11 August 2013 15:59 UTC

Return-Path: <trevp@trevp.net>
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 3725E21F9EE1 for <websec@ietfa.amsl.com>; Sun, 11 Aug 2013 08:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.397
X-Spam-Level:
X-Spam-Status: No, score=-2.397 tagged_above=-999 required=5 tests=[AWL=0.580, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 D46p-0t8Tf3V for <websec@ietfa.amsl.com>; Sun, 11 Aug 2013 08:59:02 -0700 (PDT)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id 0211921F9BF0 for <websec@ietf.org>; Sun, 11 Aug 2013 08:54:00 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id m15so4722165wgh.17 for <websec@ietf.org>; Sun, 11 Aug 2013 08:54:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tOVljYPoBQhZ0+oUkY3RMOhGgs9SNVQ7TFFK7LzbhQ0=; b=GgkVI+DhnMfXPDDkNHVsMB/4FjggiAacZBqWZkGGho6s8ZBSUkI+ANivGEDUIAYNQM IvSrCBMoSWOBFTVuXUG/zz96xalWYB3FEYkikS4pnJZQgI09tD25A5k0Z609yV38MBBl ufNYJbbOWFb1AKGDrQAAuAebx32m5sUSBL/sTUbBBKaXEWNSQ6lCs1sTxVls2aewDigW LbFjgNcz6BqQkbQQ+zobtQI6SsGoTxyP6F6JuG4UAAvLwYaXEC0LO0THyjS7OjZ5+Uu4 VnY24BH3jkVnlN4h7kYdNozmcrCwi+eAEL4OL+SVQ2hsM/w80DANml7HUnn/QjbMwMDj ipLw==
X-Gm-Message-State: ALoCoQneytXEkQM6wCV6wJ61Nk9Kfe7XV48WlVbXPwwD6P92J7c32mJc+NmRWDDarqkRXOXCy4lm
MIME-Version: 1.0
X-Received: by 10.180.78.133 with SMTP id b5mr4443447wix.17.1376236440125; Sun, 11 Aug 2013 08:54:00 -0700 (PDT)
Received: by 10.216.212.9 with HTTP; Sun, 11 Aug 2013 08:54:00 -0700 (PDT)
X-Originating-IP: [50.37.31.184]
In-Reply-To: <520776C0.9080202@gondrom.org>
References: <060.be9b0009dc0350ca543f553042673944@trac.tools.ietf.org> <073501ce8c6e$f6c17d90$e44478b0$@digicert.com> <CAMm+LwjdGJC4FHCJ_OAYGRqCGGc0Nz1pLV=yVGK9M9E7drfujQ@mail.gmail.com> <CAOuvq200e9HnPX1w9sZ+e7ipBmdgZdPL5xzKDgcaDpSxz1N=gg@mail.gmail.com> <CAMm+Lwh384YBMXw-BDoxJw+AN4qv8x6GQpF9YK4PW1gQRnadpg@mail.gmail.com> <6125A841-6C85-4858-B37F-C021067F0CFA@checkpoint.com> <2035FF99-A079-4F2F-B4DE-962FE1C1B964@checkpoint.com> <CAOuvq20O9bqHGR-5eKPmasNnWEuNW7ACL7PxM09yoTmmyt1UUg@mail.gmail.com> <CAGZ8ZG2C4uB=4vgH325TWeNW89ne4E_DN0j9ZV0t2AKa1o+x9g@mail.gmail.com> <520776C0.9080202@gondrom.org>
Date: Sun, 11 Aug 2013 08:54:00 -0700
Message-ID: <CAGZ8ZG1s2gCUZiYaj4q=+S_9M8apRPPura5YU_n8aiW9QcoQZQ@mail.gmail.com>
From: Trevor Perrin <trevp@trevp.net>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: IETF WebSec WG <websec@ietf.org>
Subject: Re: [websec] #58: Should we pin only SPKI, or also names
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 11 Aug 2013 15:59:08 -0000

On Sun, Aug 11, 2013 at 4:34 AM, Tobias Gondrom
<tobias.gondrom@gondrom.org> wrote:
> Hi all,
>
> <no hats>
>
> A small question about pinning to names and uniqueness of "pinned names":
> Under which conditions could the following attack scenario be a problem
> and what would we do about it?
>
> Domain A has bought a cert from CA-11 with the name "super safe" and
> pins to the name instead of the cert.
> CA-11 could be an intermediate for CA-1 with the name "uber super safe".
> Which names could we pin to?
> - the intermediate CA-1 and/or CA-11?
>
> Now wondering whether the following is a problem:
> attacker gains control over CA-2 (either through an attack or through
> government influence) and issues a certificate for an intermediate
> CA-11' with the name "super safe".


Yes, that's a problem.  Gerv also brought up the "DigiCert" name collision.

So using names as a "layer of indirection" to point to a set of
CA-declared keys seems better than trying to pin to names as they
appear in certs.


Trevor