Re: [TLS] Wrapping up cached info

Stefan Santesson <stefan@aaa-sec.com> Wed, 19 May 2010 17:23 UTC

Return-Path: <stefan@aaa-sec.com>
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 E1A413A688E for <tls@core3.amsl.com>; Wed, 19 May 2010 10:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[AWL=0.628, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 JiTltCR6YApq for <tls@core3.amsl.com>; Wed, 19 May 2010 10:23:14 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.94.112]) by core3.amsl.com (Postfix) with ESMTP id 6C3583A67CF for <tls@ietf.org>; Wed, 19 May 2010 10:23:11 -0700 (PDT)
Received: from s42.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id 4F02528F6E2 for <tls@ietf.org>; Wed, 19 May 2010 19:23:10 +0200 (CEST)
Received: (qmail 73061 invoked from network); 19 May 2010 17:23:03 -0000
Received: from 213-64-142-247-no153.business.telia.com (HELO [192.168.1.8]) (stefan@fiddler.nu@[213.64.142.247]) (envelope-sender <stefan@aaa-sec.com>) by s42.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <Nicolas.Williams@oracle.com>; 19 May 2010 17:23:03 -0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Wed, 19 May 2010 19:23:01 +0200
From: Stefan Santesson <stefan@aaa-sec.com>
To: Nicolas Williams <Nicolas.Williams@oracle.com>, "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
Message-ID: <C819EB15.AF55%stefan@aaa-sec.com>
Thread-Topic: [TLS] Wrapping up cached info
Thread-Index: Acr3d+6egZdGzuT38EGx5U6ojAwAVQ==
In-Reply-To: <20100519165226.GG9605@oracle.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: tls@ietf.org
Subject: Re: [TLS] Wrapping up cached info
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: Wed, 19 May 2010 17:23:15 -0000

I agree. I would rather not truncate the hash.

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.

/Stefan


On 10-05-19 6:52 PM, "Nicolas Williams" <Nicolas.Williams@oracle.com> wrote:

> On Wed, May 19, 2010 at 07:19:00AM -0700, Joseph Salowey (jsalowey) wrote:
>> To me this sounds like a good approach.  I have some questions on
>> whether the hash chosen is dependent upon the cipher suite used below.
> 
> I agree, this works for me, provided the hashes are not truncated.
> ("This" == the client caches the choice of hash function and uses that
> in its hello; if the hash function changes then the client cannot cache
> that one time, but can cache subsequently.)
> 
> Nico