Re: [TLS] draft-rescorla-tls-renegotiate and MITM resistance

David-Sarah Hopwood <david-sarah@jacaranda.org> Tue, 10 November 2009 20:16 UTC

Return-Path: <djhopwood@googlemail.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 DF49D3A68E4 for <tls@core3.amsl.com>; Tue, 10 Nov 2009 12:16:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 ux8n1mDC18o3 for <tls@core3.amsl.com>; Tue, 10 Nov 2009 12:16:16 -0800 (PST)
Received: from mail-ew0-f207.google.com (mail-ew0-f207.google.com [209.85.219.207]) by core3.amsl.com (Postfix) with ESMTP id C58053A68E7 for <tls@ietf.org>; Tue, 10 Nov 2009 12:16:15 -0800 (PST)
Received: by ewy3 with SMTP id 3so436269ewy.37 for <tls@ietf.org>; Tue, 10 Nov 2009 12:16:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type; bh=ra+lXm26g50XMUD6839YbQTZRwcbBq+x6DSzDgXrzqQ=; b=l3yhZoteK5wJ5P9/Z5ATXuGj6cAml27z9G+L0ZAIxCAOQ/F4OkVQwA8U01HDAlsd8+ CQ1n1tn6Seb9cyPA1fKEM/2kBkC8nzyUy8vW3YT/cCbURullHR4uDRYLVtAwDCGRsNK0 CwFtx7OHfXwDSxSf53+hshAp0mX5VrhC3eL+s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type; b=V4mxWFbOJ8UGY12n9xJ1HgfjhFCFr9K+0a6uacHl1cLRLxgPkciJXETjnajKymm/IS xiWVWUqXWtQnCa+kOLs1B3pfoIlPO/mheERs9Px737mqTcGiCcoxBA81iFMYXxurpwlm Ob9PVfYCoGnL3WRks5IA7Pd87Skz6hNOTMJW8=
Received: by 10.213.0.152 with SMTP id 24mr610512ebb.61.1257884197413; Tue, 10 Nov 2009 12:16:37 -0800 (PST)
Received: from ?192.168.0.2? (5e057cdf.bb.sky.com [94.5.124.223]) by mx.google.com with ESMTPS id 28sm2490454eyg.46.2009.11.10.12.16.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 10 Nov 2009 12:16:36 -0800 (PST)
Sender: David-Sarah Hopwood <djhopwood@googlemail.com>
Message-ID: <4AF9CA1B.7050407@jacaranda.org>
Date: Tue, 10 Nov 2009 20:16:27 +0000
From: David-Sarah Hopwood <david-sarah@jacaranda.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: tls@ietf.org
References: <006FEB08D9C6444AB014105C9AEB133FB36A4EBF03@il-ex01.ad.checkpoint.com> <200911092152.nA9LqVkW000963@fs4113.wdf.sap.corp> <20091109223417.GK1105@Sun.COM> <4AF8E755.5020208@extendedsubset.com> <20091110164609.GS1105@Sun.COM> <4AF9AA9E.8030603@extendedsubset.com>
In-Reply-To: <4AF9AA9E.8030603@extendedsubset.com>
X-Enigmail-Version: 0.96.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------enig54E267F9D4BFFCFBCB21375F"
Subject: Re: [TLS] draft-rescorla-tls-renegotiate and MITM resistance
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: Tue, 10 Nov 2009 20:16:17 -0000

Marsh Ray wrote:
> Is this allowed?
> 
>   |--- session A anon ---|
>   |--- session B anon ---||-- resumed A --|
> 
> I have heard that browsers may do this.

Ouch -- I thought that I understood the attack, and now you've just given
me another headache ;-)

Do servers support a renegotiation that resumes a different session?
That seems like a really bad idea.

Since a resumption may always be refused, clients can't be relying on
this behaviour. So we could compatibly specify that servers MUST NOT
accept such a resumption.

-- 
David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com