Re: [certid] Fwd: secdir review of draft-saintandre-tls-server-id-check-09

Matt McCutchen <matt@mattmccutchen.net> Thu, 16 September 2010 03:04 UTC

Return-Path: <matt@mattmccutchen.net>
X-Original-To: certid@core3.amsl.com
Delivered-To: certid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DA263A6AD9 for <certid@core3.amsl.com>; Wed, 15 Sep 2010 20:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 CxwhxNq+sKxS for <certid@core3.amsl.com>; Wed, 15 Sep 2010 20:04:20 -0700 (PDT)
Received: from homiemail-a14.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by core3.amsl.com (Postfix) with ESMTP id 045D73A6AF7 for <certid@ietf.org>; Wed, 15 Sep 2010 20:04:19 -0700 (PDT)
Received: from homiemail-a14.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTP id 301D98C06C; Wed, 15 Sep 2010 20:04:45 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=mattmccutchen.net; h=subject:from :to:cc:in-reply-to:references:content-type:date:message-id :mime-version:content-transfer-encoding; q=dns; s= mattmccutchen.net; b=dqsUYfvWF7I0mynN7vRcJkDELAYIMqU4h/dFHNyNu91 cRn9BayREOKjklDyYNg0sMeweCVdeKkliwxXhoEp19Lg9PCrRNwAp1uwY//+6SxO sO6auYFU1qWNMcjEK7aKckh1fCONNkN/IYeWPdjbzE8rNmXA7R0zoCNpmHloQJt8 =
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=mattmccutchen.net; h= subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:content-transfer-encoding; s= mattmccutchen.net; bh=OpX+AUIiBWkbxuYi/C9perdMgtU=; b=vJYZoXU7xp 09zbHDxErvQELuczoI79g/U42WtEF45XIZtXcqsklOE9WyO/EceBHEBNEEw9qw2C CHRSIftoKIdYq+ovfKOGZEOYiUXl3c6d5oxvgpWxtop/vXgqShKb5NRko9G0tXCt 0C/Fuf1pgLDS01a14f3xtG6/mafW7G8UQ=
Received: from [129.2.249.209] (ml2.student.umd.edu [129.2.249.209]) (Authenticated sender: matt@mattmccutchen.net) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTPA id B13748C06A; Wed, 15 Sep 2010 20:04:44 -0700 (PDT)
From: Matt McCutchen <matt@mattmccutchen.net>
To: Martin Rex <mrex@sap.com>
In-Reply-To: <201009160108.o8G18Sdm028897@fs4113.wdf.sap.corp>
References: <201009160108.o8G18Sdm028897@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 15 Sep 2010 23:04:43 -0400
Message-ID: <1284606283.5722.21.camel@mattlaptop2.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.4
Content-Transfer-Encoding: 7bit
Cc: certid@ietf.org
Subject: Re: [certid] Fwd: secdir review of draft-saintandre-tls-server-id-check-09
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Representation and verification of identity in certificates <certid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/certid>
List-Post: <mailto:certid@ietf.org>
List-Help: <mailto:certid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Sep 2010 03:04:21 -0000

On Thu, 2010-09-16 at 03:08 +0200, Martin Rex wrote:
> What confuses me is that 4.6.1 + 4.6.2 + 4.6.3 would allow a server,
> which originally offered an inadequate server certificate which the
> user manually confirmed, to unconditionally and silently bypass
> the users manual confirmation with appropriately looking server cert
> from any arbitrary trust anchor.  This doesn't seem right.

I disagree.  The user's confirmation was to accept the certificate, not
to use it exclusively.  I have taken advantage of this behavior on
https://mattmccutchen.net .

> The option of memorizing a server certificate for future reconnects
> would significantly improve the security.  Once a client caches
> a server cert that is manually confirmed by the user, this could
> protect a user on future reconnects to the same server from
> an attacker that succeeds subverting a trusted CA.  Even from
> full compromise of all CAs by that attacker.  

The certificate exception mechanism serves the limited purpose of making
it possible for users to connect to servers with unverifiable
certificates, without which they would be unable to get work done in
some cases.  It looks like you're trying to replace the public-CA trust
model, which is a much more ambitious goal, and it's not clear that your
suggested change to the exception mechanism is anything near an
appropriate or comprehensive solution.  Let's have that discussion
elsewhere and let the server-id-check draft proceed with its original
scope.

-- 
Matt