Re: [TLS] Wrapping up cached info

"Brian Smith" <> Sun, 23 May 2010 21:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 97B0A3A6D16 for <>; Sun, 23 May 2010 14:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[AWL=-0.464, BAYES_50=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id q1KJPGUHkqrv for <>; Sun, 23 May 2010 14:40:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A70333A6D1C for <>; Sun, 23 May 2010 14:40:56 -0700 (PDT)
Received: from T60 (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id AD3D2509DB; Sun, 23 May 2010 17:40:42 -0400 (EDT)
From: "Brian Smith" <>
To: "'Stefan Santesson'" <>, <>
References: <> <>
In-Reply-To: <>
Date: Sun, 23 May 2010 16:40:41 -0500
Message-ID: <003201cafac0$9a75d9c0$cf618d40$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQLQ7/4q/KLQVzxL8sxVWEl+M5k3YwIitPLtAc+v0M0=
Subject: Re: [TLS] Wrapping up cached info
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 23 May 2010 21:40:57 -0000

Stefan Santesson wrote:
> I will, provided that this seems acceptable still in a few days from now,
> write up a new draft that captures the changes which then hopefully can be
> ready for a WGLC.

There's another issue still. If the server sends the client an information
item X after the change cipher suite message, then the client must not send
a hash of that information item in its client hello message on another
connection, until it has verified the identity of the server on that second
connection. In other words, the client must ensure that it doesn't leak
information that would otherwise be confidential--including even certificate
messages and client certificate cipher suite messages that were received
over an encrypted connection.