Re: [TLS] Cached-info substitution

Brian Smith <> Fri, 19 February 2010 15:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6FE963A7EB6 for <>; Fri, 19 Feb 2010 07:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id smdMAbza2A1k for <>; Fri, 19 Feb 2010 07:38:12 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id B3C313A7CE8 for <>; Fri, 19 Feb 2010 07:38:12 -0800 (PST)
Received: from [] (unknown []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id B34C922E254; Fri, 19 Feb 2010 10:39:52 -0500 (EST)
Message-ID: <>
Date: Fri, 19 Feb 2010 09:39:55 -0600
From: Brian Smith <>
User-Agent: Postbox 1.1.1 (Windows/20100208)
MIME-Version: 1.0
To: Stefan Santesson <>
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [TLS] Cached-info substitution
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: Fri, 19 Feb 2010 15:38:13 -0000

Stefan Santesson wrote:
> I like in principle your suggested simplification to omit whole handshake
> messages to indicate substitution. However, this works only if the cached
> parameter is the only parameter of the handshake message. I.e. It works for
> the server Certificate message but not for the certificate_authorities
> parameter of the CertificateRequest message.
That's why I suggested to treat a zero-length 
CertificateRequest.certificate_authorities (encoded "0x00 0x00") as "use 
the cached value" if and only if the server hello says that the server 
supports caching it. Maybe it is also possible to treat a zero-length 
Certificate.certificate_list ("0x00 0x00 0x00") as "use the cached 
value" if and only if the server hello says the server supports caching 
it. I suggested omitting the Certificate message completely only because 
I am not sure if any cipher suites allow zero-length certificate lists 
for another reason.