Re: [TLS] Security concerns around co-locating TLS and non-secure on same port (WGLC: draft-ietf-tsvwg-iana-ports-08)

Nico Williams <nico@cryptonector.com> Thu, 10 February 2011 02:25 UTC

Return-Path: <nico@cryptonector.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 A23BE3A680C; Wed, 9 Feb 2011 18:25:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.177
X-Spam-Level:
X-Spam-Status: No, score=-1.177 tagged_above=-999 required=5 tests=[AWL=0.800, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 TM+HQMHYv3XJ; Wed, 9 Feb 2011 18:25:32 -0800 (PST)
Received: from homiemail-a72.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by core3.amsl.com (Postfix) with ESMTP id EA9963A67FA; Wed, 9 Feb 2011 18:25:31 -0800 (PST)
Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id 8E0736B0073; Wed, 9 Feb 2011 18:25:42 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=AeFtmH35WiEtK2PJpAsLy 3YXsRltHaXRR5BqRZdkb8g8njR9iFcj+5k8ezhMRcOpE9A2F1I39sQBGr66mwSUF lz5SBfW0NH48Ju7A/NbWRKFwU8IeQh2FafoCsoGLlhnPxVTQjGRTAb/9qjP5cqNp 2SmRZ+vwEJvN0Z9q7ZlOII=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=vDkjkl0kvw1VKvuxPiX3 S346h/g=; b=VvNWTDtbVTTTzY99Wa0yRarmCZGr28lQR9j9cJmO4HHOLD/ub/tH 15UTE40gza4P4amsyfjd2mWTrxWDV8DNJpIEBpq3i6jFN7u1RDRThYP14RUcDkmW vJtXdi9jezqzamNIjAvRXKSmbRsN4iboEBUXeE3fyQ+xtQCmBcbaERE=
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTPSA id 55B736B0070; Wed, 9 Feb 2011 18:25:42 -0800 (PST)
Received: by gxk27 with SMTP id 27so416189gxk.31 for <multiple recipients>; Wed, 09 Feb 2011 18:25:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.32.16 with SMTP id f16mr2083595agf.202.1297304741429; Wed, 09 Feb 2011 18:25:41 -0800 (PST)
Received: by 10.90.103.11 with HTTP; Wed, 9 Feb 2011 18:25:41 -0800 (PST)
In-Reply-To: <D8B3FDB7A62612A570324BEB@nifty-silver.us.oracle.com>
References: <4CD76B1B.5030308@ericsson.com> <D8B3FDB7A62612A570324BEB@nifty-silver.us.oracle.com>
Date: Wed, 09 Feb 2011 20:25:41 -0600
Message-ID: <AANLkTi=80p2Yjqgopj98r4SFhbQgxC_tnfvPcCUGuuhg@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Chris Newman <chris.newman@oracle.com>
Content-Type: text/plain; charset="UTF-8"
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, tls@ietf.org, tsvwg <tsvwg@ietf.org>
Subject: Re: [TLS] Security concerns around co-locating TLS and non-secure on same port (WGLC: draft-ietf-tsvwg-iana-ports-08)
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: Thu, 10 Feb 2011 02:25:32 -0000

On Wed, Feb 9, 2011 at 8:12 PM, Chris Newman <chris.newman@oracle.com> wrote:
> I know I'm very late on this topic, but my position differs from others so
> I'll comment.

+1

But I'll also add that it's not necessarily harder for implementers to
manage StartTLS with isolation.  I realize that implementers have
screwed this up in the past, but there is hope that we can learn, and
even develop institutional memory -- if not we have other problems.

Nico
--