Re: [saag] Channel binding is great but not a silver bullet

Stephen Kent <kent@bbn.com> Tue, 03 March 2009 00:24 UTC

Return-Path: <kent@bbn.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD49028C1F9 for <saag@core3.amsl.com>; Mon, 2 Mar 2009 16:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.176
X-Spam-Level:
X-Spam-Status: No, score=-2.176 tagged_above=-999 required=5 tests=[AWL=0.423, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3nJZ9kE0+72L for <saag@core3.amsl.com>; Mon, 2 Mar 2009 16:24:14 -0800 (PST)
Received: from mx3.bbn.com (mx3.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id DAD9C28C205 for <saag@ietf.org>; Mon, 2 Mar 2009 16:23:07 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15] helo=[10.71.0.151]) by mx3.bbn.com with esmtp (Exim 4.63) (envelope-from <kent@bbn.com>) id 1LeIQ1-0006Ab-Bt; Mon, 02 Mar 2009 19:23:33 -0500
Mime-Version: 1.0
Message-Id: <p06240800c5d2020dabec@[128.89.89.88]>
In-Reply-To: <20090302160035.GF9992@Sun.COM>
References: <2788466ED3E31C418E9ACC5C3166155768B2CB@mou1wnexmb09.vcorp.ad.vrsn.com> <0c2301c9979f$8a1cd770$0600a8c0@china.huawei.com> <2788466ED3E31C418E9ACC5C3166155768B2CE@mou1wnexmb09.vcorp.ad.vrsn.com> <20090226143809.GF7227@mit.edu> <1235663917.3293.16.camel@localhost> <20090226165448.GK9992@Sun.COM> <tslprh5rlvt.fsf_-_@mit.edu> <20090302160035.GF9992@Sun.COM>
Date: Mon, 02 Mar 2009 19:22:31 -0500
To: Nicolas Williams <Nicolas.Williams@sun.com>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: saag@ietf.org
Subject: Re: [saag] Channel binding is great but not a silver bullet
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 00:24:14 -0000

Nico,

I'm unclear on the exact constraints you're trying to satisfy with 
the channle binding model, but here are some observations anyway.

Mutual authentication is certainly desirable for most communication 
contexts. But, in contexts where neither party has a relationship 
with the other a priori, I don't think there is any magic bullet.

The primary, large scale, global PKI to which PHB alluded is the only 
major example we have where a user can get a reasonable level of 
assurance for one-way authentication. That model enables a 
(conceptually simple) transition to two-way, cert-based 
authentication, where each web site can act as a CA for its users. 
However, the poor tools we have to manage a plethora of certs from 
these narrowly-scoped CAs makes it hard for users to buy into that 
model.

In other parts of the world (especially in Asia)) there are large 
PKIs that serve substantial user communities. Often governments take 
the lead in issuing certs to individuals in these PKIs, and in 
creating CAs or bridge CAs to certify government and private sector 
organizations.

But, none of this is free. Absent government subsidies, mandated use, 
or hidden taxes, one ought not surprised by business models that 
require users and/or web site owners to pay for certs.  After all, in 
most contexts, at best you get what you pay for :-).

The lack of a single credential that authenticates a user to 
everywhere is a good thing from a privacy perspective. Federated 
identity management schemes create lots of opportunities to link 
islands of authenticated users (and organizations), but they have 
sever drawbacks re security. I tend to think of such schemes as 
having all the charming features of Wikipedia :-).

Steve