Re: [TLS] matching identity, by default

Marsh Ray <marsh@extendedsubset.com> Fri, 04 December 2009 00:34 UTC

Return-Path: <marsh@extendedsubset.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 F00493A6804 for <tls@core3.amsl.com>; Thu, 3 Dec 2009 16:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level:
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 CGFxpYHMKYny for <tls@core3.amsl.com>; Thu, 3 Dec 2009 16:34:53 -0800 (PST)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by core3.amsl.com (Postfix) with ESMTP id 466AA3A67D4 for <tls@ietf.org>; Thu, 3 Dec 2009 16:34:53 -0800 (PST)
Received: from xs01.extendedsubset.com ([69.164.193.58]) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.68) (envelope-from <marsh@extendedsubset.com>) id 1NGM8C-000Lzk-Gz; Fri, 04 Dec 2009 00:34:44 +0000
Received: from [127.0.0.1] (localhost [127.0.0.1]) by xs01.extendedsubset.com (Postfix) with ESMTP id E51B1603C; Fri, 4 Dec 2009 00:34:43 +0000 (UTC)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 69.164.193.58
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+qOXeXYUjB944MyDZtEDDnl3mMW3mYSw0=
Message-ID: <4B185921.5040106@extendedsubset.com>
Date: Thu, 03 Dec 2009 18:34:41 -0600
From: Marsh Ray <marsh@extendedsubset.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: David-Sarah Hopwood <david-sarah@jacaranda.org>
References: <C2329F9D-F5EF-4E8B-9EE8-ED246D7B7287@manger.com.au> <BF782069-544A-4842-B8C8-A9472C9794BB@acm.org> <4B17C2F9.9010802@extendedsubset.com> <A1ECF717-4E06-4654-8B1D-7FDE6C5A2F24@acm.org> <4B18096E.20805@extendedsubset.com> <4B185802.6070306@jacaranda.org>
In-Reply-To: <4B185802.6070306@jacaranda.org>
X-Enigmail-Version: 0.96.0
OpenPGP: id=1E36DBF2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: tls@ietf.org
Subject: Re: [TLS] matching identity, by default
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: Fri, 04 Dec 2009 00:34:54 -0000

David-Sarah Hopwood wrote:
> Marsh Ray wrote:
>> * The TLS protocol allows application data to be interleaved within
>> rengotiation handshake messages. Sometimes this is desired, but may
>> require extra care. The application-supplied callback and TLS library
>> normally SHOULD discard any buffered plaintext at the point of
>> renegotiation.
> 
> I appreciate the problem that this recommendation is trying to solve,
> but as stated here it may do more harm than good. Discarding any plaintext
> may cause the application protocol states at the client and server to
> lose synchronization, creating a vulnerability, or at least incorrect
> behaviour.

Good point. It certainly "requires extra care".

Ideally the app layer would be defined to discard all state and buffered
data at the point of renegotiation, too.

- Marsh