Re: [CHANNEL-BINDING] [sasl] Updates to draft-altman-tls-channel-bindings, take two (PLEASE REVIEW)

Nicolas Williams <Nicolas.Williams@sun.com> Tue, 23 March 2010 19:07 UTC

Return-Path: <Nicolas.Williams@sun.com>
X-Original-To: channel-binding@core3.amsl.com
Delivered-To: channel-binding@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF4463A6B42; Tue, 23 Mar 2010 12:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.774
X-Spam-Level:
X-Spam-Status: No, score=-2.774 tagged_above=-999 required=5 tests=[AWL=1.206, BAYES_05=-1.11, DNS_FROM_OPENWHOIS=1.13, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 PAayT8l1oW4T; Tue, 23 Mar 2010 12:07:19 -0700 (PDT)
Received: from rcsinet11.oracle.com (rcsinet11.oracle.com [148.87.113.123]) by core3.amsl.com (Postfix) with ESMTP id E5CE93A69B5; Tue, 23 Mar 2010 12:07:18 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet11.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o2NJ7Qkx014868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 23 Mar 2010 19:07:36 GMT
Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o2NJ7OE0029620; Tue, 23 Mar 2010 19:07:24 GMT
Received: from abhmt008.oracle.com by acsmt354.oracle.com with ESMTP id 104532511269371194; Tue, 23 Mar 2010 12:06:34 -0700
Received: from Sun.COM (/129.153.128.104) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 23 Mar 2010 12:06:34 -0700
Date: Tue, 23 Mar 2010 14:06:29 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: channel-binding@ietf.org, sasl@ietf.org, tls@ietf.org, Mark Novak <Mark.Novak@microsoft.com>, Larry Zhu <lzhu@wollive.windowsmedia.com.akadns.net>
Message-ID: <20100323190629.GR21244@Sun.COM>
References: <20100317231522.GA18167@Sun.COM> <20100322232150.GB21244@Sun.COM> <20100323065301.GE21244@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20100323065301.GE21244@Sun.COM>
User-Agent: Mutt/1.5.20 (2010-03-02)
X-Source-IP: acsmt353.oracle.com [141.146.40.153]
X-Auth-Type: Internal IP
X-CT-RefId: str=0001.0A090204.4BA9116D.02AE,ss=1,fgs=0
Cc: Pasi Eronen <pasi.eronen@nokia.com>
Subject: Re: [CHANNEL-BINDING] [sasl] Updates to draft-altman-tls-channel-bindings, take two (PLEASE REVIEW)
X-BeenThere: channel-binding@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of channel binding IANA registry requests and specifications <channel-binding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/channel-binding>
List-Post: <mailto:channel-binding@ietf.org>
List-Help: <mailto:channel-binding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 19:07:20 -0000

On Tue, Mar 23, 2010 at 01:53:01AM -0500, Nicolas Williams wrote:
> On Mon, Mar 22, 2010 at 06:21:50PM -0500, Nicolas Williams wrote:
> > I've posted -08 of draft-altman-tls-channel-bindings:
> 
> I forgot to describe the synchronization problem that Simon pointed out,
> as well as the solution.
> 
> I'll file -09 tomorrow.

Submitted:

http://www.ietf.org/id/draft-altman-tls-channel-bindings-09.txt

Larry, Mark,

It occurs to me that it must be very unlikely that any apps using the
MSFT variant of tls-unique are doing authentication after TLS
re-negotiation.  We already have confirmation that in the HTTP/Negotiate
case that never happens.  If so, might you be willing to fix your
implementation to always use the initial handshake?  That would help
remove two pieces of complexity from -09: a) security considerations with
regard to the TLS re-negotiation bug, b) interoperability considerations
with regard to the channel binding synchronization problem.

Nico
--