Re: [TLS] Encrypting record headers: practical for TLS 1.3 after all?

Viktor Dukhovni <ietf-dane@dukhovni.org> Thu, 03 December 2015 04:33 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 748BC1B300D for <tls@ietfa.amsl.com>; Wed, 2 Dec 2015 20:33:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 pvqmFYBdwtXh for <tls@ietfa.amsl.com>; Wed, 2 Dec 2015 20:33:45 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F021B300B for <tls@ietf.org>; Wed, 2 Dec 2015 20:33:44 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id C7C06284E35; Thu, 3 Dec 2015 04:33:43 +0000 (UTC)
Date: Thu, 03 Dec 2015 04:33:43 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: tls@ietf.org
Message-ID: <20151203043343.GD18315@mournblade.imrryr.org>
References: <CAFggDF3HP5u0YP0UP_HrrZnrTnzc-CD1EG0grZBcb5sB7A2fAA@mail.gmail.com> <20151202160837.6016A1A39B@ld9781.wdf.sap.corp> <CAFggDF0D3Rgav-4xg-11u0igMyMXvAWT+JNt2r1xyQnpvm08Qw@mail.gmail.com> <0ba184c45d44474e961a2aaac82fec0e@usma1ex-dag1mb1.msg.corp.akamai.com> <CAFggDF119jxPSXUAe2E4y_TQds4P3K1eTGM3sZHSa=NoeMOV-A@mail.gmail.com> <1b5cf52ca90e45bd82f5247ca675dead@usma1ex-dag1mb1.msg.corp.akamai.com> <CAFggDF24hhrXS95kONb_N6XHrO+11wFsAkHOpYZ_uu5RvyV+Kg@mail.gmail.com> <60e21928e9174d8ea7eb84b00ad85884@usma1ex-dag1mb1.msg.corp.akamai.com> <CAFggDF3wehZX9meomiAx0A79qPemmhrBs9c8cqJSqMYiDJ7iUw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAFggDF3wehZX9meomiAx0A79qPemmhrBs9c8cqJSqMYiDJ7iUw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/JXGb7hVOXb6ZFZNa9LtVNdcU2iU>
Subject: Re: [TLS] Encrypting record headers: practical for TLS 1.3 after all?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tls@ietf.org
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 Dec 2015 04:33:46 -0000

On Thu, Dec 03, 2015 at 03:49:02AM +0000, Jacob Appelbaum wrote:

> > It is far from clear that the privacy gains anything in the form of
> > practical protection.  Having looked at it, I'm unconvinced.  And I've been
> > a privacy/crypto advocate for a very very long time.
> 
> I resolve DNS through Tor and so in that case, my TLS connections
> often exit over a different circuit. My TLS connection would not
> otherwise leak the host I'm requesting if the protocol had a way to
> protect that data. It doesn't. The protocol leak is the problem.

The most compelling argument for SNI encryption I took away from
this thread the cheap opportunity for blocking traffic based on
cleartext SNI.  Of course SNI encryption can't help if the destination
IP address supports one or a very few related domains, but it could
help otherwise.

Of course nation-states willing to play hardball will work-around
the problem, but they are doing that even without encrypted SNI.

[ Those of you on the crypto list will have seen the announcement
  about Kazakhstan mandating a national security certificate which
  must be installed on all customer devices that use the Internet... ]

-- 
	Viktor.