Re: [TLS] Accepting that other SNI name types will never work.

Richard Moore <rich@kde.org> Thu, 03 March 2016 22:52 UTC

Return-Path: <richmoore44@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB8B91B2EF7 for <tls@ietfa.amsl.com>; Thu, 3 Mar 2016 14:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level:
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NON1O7Hw-hJx for <tls@ietfa.amsl.com>; Thu, 3 Mar 2016 14:52:37 -0800 (PST)
Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54F121B2EF8 for <tls@ietf.org>; Thu, 3 Mar 2016 14:52:37 -0800 (PST)
Received: by mail-yk0-x229.google.com with SMTP id 1so15916911ykg.3 for <tls@ietf.org>; Thu, 03 Mar 2016 14:52:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=1EHlWMQ7XmnVgC+zZG3yKmXxw5Atd6j5ya9T5jFw0Yw=; b=qUXzDEsL6n407mLPe7QWfhjtb+t5uFT09LlFe6lFKmn7jgQM77k31N2zUQsKWf547n pJvKShrQopeEetkC31POksCJ9sEybvHUneBH/PTkfa1sdlNOMQRfLi0nzxC/MK0lM2ML NBhQJ/efF4HEG+4cdFPgRqEI9gJsvMfvJrUntbleXbW8O0OK35CoYRmmpYktIZE0u64E jKrT7QXD3pAmM4w97CHb0YBCcSFQofmif6/4e5sMS7IKNwmPSLaji0+w5FDi9Mzcv8va qpaYhtx6y3ONKmQV1zz2zEnTDU0gI4dRqwcY7lko8A7SIMaL8qPIb2zY0zY7ihWho0TN ECuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=1EHlWMQ7XmnVgC+zZG3yKmXxw5Atd6j5ya9T5jFw0Yw=; b=bRpen8ChcAdHytW9KQrLamZoX0GhOwjgV4wscDYW8TRHCTEbHNmFGl8Kl49C2XIkEv qoF0fvXXR14ZVcpd6sQOnWBQtgKmg8ZdDynYWpNepl8uI3YSARRyYIe+C2wUgR1uMzQf yqU5e0hDFOLF0HuTksmJ3hu99gtz4JGsVmwZmRP3m3a89j9rHt5fbS58PyMFQ/7H8a77 xWm8OV6s2SWkoSCQexzi6HiVoU/WozaK07IWKNohS1UuNtzp9jj/6Awmx0jZR0DItQuB FnoRaKaC3o+6/hQepqJtwXqSGY3AMtBVjx8tKugbNPRzn/8NLZz9eWLuNRY5KyiZG2no ABAQ==
X-Gm-Message-State: AD7BkJKQgntgPi1AbVfym8DQogF/tXXe5uX2PQvmsCFChCNfZmZWgGms6LD3SIiMwLnwFLKdC0JPPpkry1KFnw==
MIME-Version: 1.0
X-Received: by 10.37.29.193 with SMTP id d184mr3116691ybd.111.1457045556473; Thu, 03 Mar 2016 14:52:36 -0800 (PST)
Sender: richmoore44@gmail.com
Received: by 10.37.4.139 with HTTP; Thu, 3 Mar 2016 14:52:36 -0800 (PST)
In-Reply-To: <CABkgnnWd_4F-J5m8vtR2fNtKg+1sB=HVAr=w0CPT6W+31g_Kgg@mail.gmail.com>
References: <CAMfhd9WNHqfRH=M=_B7_apJ-r43fi8qoe-+VcDkrKPwwhkPR5A@mail.gmail.com> <CABkgnnWd_4F-J5m8vtR2fNtKg+1sB=HVAr=w0CPT6W+31g_Kgg@mail.gmail.com>
Date: Thu, 3 Mar 2016 22:52:36 +0000
X-Google-Sender-Auth: dr5dqbsJ3a86Ah8gWiUqivnEV2A
Message-ID: <CAMp7mVtwrF9CL-MqyF0UZJemBOMyFieAy++-_539fE5eAB_KMQ@mail.gmail.com>
From: Richard Moore <rich@kde.org>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a11427890d0b57f052d2cda47
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/ty6fsrGDMYDuKjTF06X2UQ5YxYg>
Cc: Adam Langley <agl@imperialviolet.org>, "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Accepting that other SNI name types will never work.
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Mar 2016 22:52:39 -0000

If you're fixing that then maybe standardising the errors makes sense too.
My fingerprinter sees the following:

For an empty name:

SNIEmptyName: *(301)alert:DecodeError:fatal|
SNIEmptyName: *(301)alert:HandshakeFailure:fatal|
SNIEmptyName: *(301)alert:IllegalParameter:fatal|
SNIEmptyName: *(303)alert:UnexpectedMesage:fatal|
SNIEmptyName: error:Unexpected EOF receiving record header - server closed
connection|

For a long name (x repeated 500 times):

SNILongName: *(301)alert:HandshakeFailure:fatal|
SNILongName: *(301)alert:IllegalParameter:fatal|
SNILongName: *(301)alert:UnrecognizedName:fatal|
SNILongName: *(303)alert:UnexpectedMesage:fatal|
SNILongName: error:Unexpected EOF receiving record header - server closed
connection|

Rich.


On 3 March 2016 at 22:44, Martin Thomson <martin.thomson@gmail.com> wrote:

> On 4 March 2016 at 05:49, Adam Langley <agl@imperialviolet.org> wrote:
> > (I think the lesson here is that protocols should have a single joint,
> > and that it should be kept well oiled. For TLS, that means that
> > extensions should have minimal extensionality in themselves and that
> > we should generally rely on the main extensions mechanism for these
> > sorts of things.)
>
> Big +1
>
> Note that the NSS bug also entailed non-zero SNI name types
> overwriting the actual SNI.
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>