Re: [TLS] Two Opaque Values in Renegotiation_Info (was Re: webex)

Bodo Moeller <bmoeller@acm.org> Sun, 15 November 2009 19:58 UTC

Return-Path: <bmoeller@acm.org>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F192C3A6765 for <tls@core3.amsl.com>; Sun, 15 Nov 2009 11:58:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.848
X-Spam-Level:
X-Spam-Status: No, score=-99.848 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_50=0.001, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
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 SlMjv6J8Mxv4 for <tls@core3.amsl.com>; Sun, 15 Nov 2009 11:58:26 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by core3.amsl.com (Postfix) with ESMTP id 04F573A635F for <tls@ietf.org>; Sun, 15 Nov 2009 11:58:23 -0800 (PST)
Received: from [192.168.1.3] (c-76-102-12-92.hsd1.ca.comcast.net [76.102.12.92]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MSVhA-1NbDiv48pA-00S18z; Sun, 15 Nov 2009 20:58:20 +0100
From: Bodo Moeller <bmoeller@acm.org>
To: Eric Rescorla <ekr@networkresonance.com>
In-Reply-To: <20091113231013.8676669F516@kilo.networkresonance.com>
References: <4AFC5D80.2030101@pobox.com> <AC1CFD94F59A264488DC2BEC3E890DE5091A715F@xmb-sjc-225.amer.cisco.com> <4AFD91D1.7030409@pobox.com> <4AFDB8DF.4010608@pobox.com> <20091113231013.8676669F516@kilo.networkresonance.com>
Message-Id: <54186B27-2E2C-4DCD-B8C5-7239FBABB631@acm.org>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sun, 15 Nov 2009 11:58:15 -0800
X-Mailer: Apple Mail (2.936)
X-Provags-ID: V01U2FsdGVkX1+hQU55dOz1WObxB9CRH2CAx+4Z65VtxB1e5hw m2qaivz3bxD4J5MlMpfWGFe73Q4kM88q0bj/4qfiZf9qRlsgOS DztoyEfg2SlelX1911BqQ==
Cc: tls@ietf.org
Subject: Re: [TLS] Two Opaque Values in Renegotiation_Info (was Re: webex)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Nov 2009 19:58:27 -0000

On Nov 13, 2009, at 3:10 PM, Eric Rescorla wrote:

> At Fri, 13 Nov 2009 11:51:59 -0800,
> Michael D'Errico wrote:

>> I noticed in the logs that there was discussion of wanting to
>> have two separate opaque values, I assume one for the client
>> verify data and the other for the server verify data.

> As far as I know this is not being actively considered.

There's no point in having these two values sent in the same message.   
Using two fields would break backwards compatibility with draft- 
rescorla-tls-renegotiation-00.txt -- but backwards compatibility with  
this would be the only reason to keep the client's verify_data in the  
server's extension.

Bodo