Re: [TLS] assert TLSext in renego-ServerHello instead of disable renego

Marsh Ray <marsh@extendedsubset.com> Sun, 15 November 2009 20:22 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 56BAD3A6827 for <tls@core3.amsl.com>; Sun, 15 Nov 2009 12:22:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level:
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[AWL=1.177, 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 HXSCKqNhfipS for <tls@core3.amsl.com>; Sun, 15 Nov 2009 12:22:38 -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 D9C013A68FD for <tls@ietf.org>; Sun, 15 Nov 2009 12:22:06 -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 1N9lbq-0008tW-0J for tls@ietf.org; Sun, 15 Nov 2009 20:22:06 +0000
Received: from [127.0.0.1] (localhost [127.0.0.1]) by xs01.extendedsubset.com (Postfix) with ESMTP id E17AC667C for <tls@ietf.org>; Sun, 15 Nov 2009 20:22:04 +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/Z1K44YMQQ0tI47HkAPQCXhXqZGV7Uf4A=
Message-ID: <4B0062EA.8060906@extendedsubset.com>
Date: Sun, 15 Nov 2009 14:22:02 -0600
From: Marsh Ray <marsh@extendedsubset.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "tls@ietf.org" <tls@ietf.org>
References: <200911092035.nA9KZviE026489@fs4113.wdf.sap.corp> <4AF8EF8F.3090100@jacaranda.org> <4AF8F7B4.7020101@pobox.com> <4AF8FDBD.4080003@jacaranda.org> <4AF9070E.4050305@jacaranda.org> <4AF99E04.3060604@pobox.com> <20091112055910.58D2369EF16@kilo.networkresonance.com> <4AFC46D8.9050905@pobox.com> <20091113060004.55DC569F31E@kilo.networkresonance.com> <3494BBB0-E80A-4CCA-92EF-A7EC794BEF9D@acm.org> <4B005E54.6030600@extendedsubset.com> <FD7FB19E-2A6B-48FA-9DAD-D0C4835C22EF@acm.org>
In-Reply-To: <FD7FB19E-2A6B-48FA-9DAD-D0C4835C22EF@acm.org>
X-Enigmail-Version: 0.96.0
OpenPGP: id=1E36DBF2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [TLS] assert TLSext in renego-ServerHello instead of disable renego
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: Sun, 15 Nov 2009 20:22:39 -0000

Bodo Moeller wrote:
>
> Arguably I'd rather have monitoring tell me about clients that will
> *tolerate* a handshake with a server that doesn't support the extension
> (not so much about clients that don't support the extension at all).  In
> that case, I wouldn't want these clients to send the extension on the
> initial handshake.

Good point.

These systems will probably spot unsafe renegotiations happening.

It may be that we need two bits: 'endpoint patched' and 'endpoint
configured secure'.

- Marsh