Re: [TLS] Wrapping up cached info

Simon Josefsson <simon@josefsson.org> Mon, 17 May 2010 15:19 UTC

Return-Path: <simon@josefsson.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 9DEA03A6A74 for <tls@core3.amsl.com>; Mon, 17 May 2010 08:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level:
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599]
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 iEUp8+reWMej for <tls@core3.amsl.com>; Mon, 17 May 2010 08:19:31 -0700 (PDT)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id B31CC28C12C for <tls@ietf.org>; Mon, 17 May 2010 08:17:31 -0700 (PDT)
Received: from mocca (c80-216-25-148.bredband.comhem.se [80.216.25.148]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id o4HFHHxf009696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 17 May 2010 17:17:18 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@oracle.com>
References: <Pine.LNX.4.44.1005132018460.13071-100000@citation2.av8.net> <C8171810.ADE4%stefan@aaa-sec.com> <20100517145738.GQ9429@oracle.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:100517:stefan@aaa-sec.com::bYj6xAy1CUMZRNK6:2gfX
X-Hashcash: 1:22:100517:tls@ietf.org::oPBFSvhjSJOzBrn9:A1b4
X-Hashcash: 1:22:100517:nicolas.williams@oracle.com::j5lPvtQZiw27/rzy:UeQe
Date: Mon, 17 May 2010 17:17:17 +0200
In-Reply-To: <20100517145738.GQ9429@oracle.com> (Nicolas Williams's message of "Mon, 17 May 2010 09:57:38 -0500")
Message-ID: <87tyq6woaq.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: clamav-milter 0.96 at yxa-v
X-Virus-Status: Clean
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: Mon, 17 May 2010 15:19:34 -0000

Nicolas Williams <Nicolas.Williams@oracle.com> writes:

> I believe the only obvious and simple way to prevent such attacks and,
> crucially, simplify the security analysis of this protocol, is to bind
> the cached objects' data into the handshake, almost as if they'd not
> been cached in the first place.

+1.  I think this is a good extension for Paul's additional random input
framework.

/Simon