Re: [secdir] review of draft-hollenbeck-rfc4933bis-02

Nicolas Williams <Nicolas.Williams@sun.com> Thu, 16 July 2009 15:26 UTC

Return-Path: <Nicolas.Williams@sun.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C435928C180; Thu, 16 Jul 2009 08:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.767
X-Spam-Level:
X-Spam-Status: No, score=-5.767 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 OUd5SBj-mQMB; Thu, 16 Jul 2009 08:26:53 -0700 (PDT)
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by core3.amsl.com (Postfix) with ESMTP id 3B5EB3A6D8F; Thu, 16 Jul 2009 08:26:53 -0700 (PDT)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n6GFREoJ016707; Thu, 16 Jul 2009 15:27:14 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n6GFREuZ015833; Thu, 16 Jul 2009 09:27:14 -0600 (MDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n6GFGtdF009378; Thu, 16 Jul 2009 10:16:55 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n6GFGslg009377; Thu, 16 Jul 2009 10:16:54 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Thu, 16 Jul 2009 10:16:54 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: "Polk, William T." <william.polk@nist.gov>
Message-ID: <20090716151653.GX1274@Sun.COM>
References: <4A5F0C80.10504@isode.com> <C684B760.11AC5%tim.polk@nist.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C684B760.11AC5%tim.polk@nist.gov>
User-Agent: Mutt/1.5.7i
Cc: "secdir@ietf.org" <secdir@ietf.org>, "Hollenbeck, Scott" <shollenbeck@verisign.com>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [secdir] review of draft-hollenbeck-rfc4933bis-02
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2009 15:26:54 -0000

On Thu, Jul 16, 2009 at 10:54:24AM -0400, Polk, William T. wrote:
> > Nico's response confirmed what I was thinking about this myself: for EPP
> > running over TLS over TCP (4934bis), channel bindings are not required,
> > because TLS authentication is mandatory and because TLS server
> > certificate verification procedure is also mandatory.
> > So I don't think there is an issue with 4934bis document.
> 
> I'm not so sure... TLS server certificate verification protects the client
> against a MITM attack.  The server has no way of knowing whether this
> procedure has been implemented.  So, the server does not have all the
> protection it needs unless the TLS connection uses client certificate
> authentication as well.
> 
> Channel bindings would extend the level of assurance for the server.
> Alternatively, mutual authentication using certificates would resolve the
> problem as well.

The client can always just post the username & password in a very public
place, spam people with it, ...

Channel binding doesn't protect against that!  ;)