IETF Logo Mail Archive

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

Aaron Zauner <azet@azet.org> Thu, 03 December 2015 16:44 UTC

Return-Path: <azet@azet.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 B7C371A90F9 for <tls@ietfa.amsl.com>; Thu, 3 Dec 2015 08:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 fpc-thFCKETz for <tls@ietfa.amsl.com>; Thu, 3 Dec 2015 08:44:13 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (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 501B01A90F8 for <tls@ietf.org>; Thu, 3 Dec 2015 08:44:13 -0800 (PST)
Received: by lbcdv4 with SMTP id dv4so5150524lbc.2 for <tls@ietf.org>; Thu, 03 Dec 2015 08:44:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=azet.org; s=gmail; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=1ZgKLCtEX7a9OrEzGwgJ5FoZFuKcIvzbwXI7nkkYGyQ=; b=hIzhL24z3EqZDR/uUNvrF2MwtZJhgiBhimaXmqyheweqpvfNmX4jlA9EKY3GFtxxuS p0WgOk/AdoQlBOJOrkH9Hu2vBPq5VHh/B2KGBNZ6CQm3Zw3eWpjbXLQLClyCCQS/1zN7 BF7x943KxbOURsJ43Gc2ppNXzUTZN0KDqObcY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=1ZgKLCtEX7a9OrEzGwgJ5FoZFuKcIvzbwXI7nkkYGyQ=; b=MRQe8VvzC7klbExSM7yezsgbQ0f3/1nlRHm8o/lKwPUk+J5LnaLGiCFWfs9OFelyjW hMq4bjK92rdmD7STzWSKNDzhOjlqS3+rxD2ahtT/7wGzEZqLYtgJzWVO9P8Jmji9faK8 fSay6cz4nyNnj6RaKA/U1UFxIGoGrE4TUN529UrzczG0rnpKDOyNIrarLs6npcedbHtn p4qOUlkOMHSqFW0Mhih9ZN2e9oYUAnCwsVVkF4Zyb5QRwRF+YG3GAZy93GzZ5U/nbGol Dn/SRPj0AxWg9cfm6OuRLSx8KZVZkRV4BSPLh85ZkYfyNxKG4MpaQQ/C6ulk7MF6C+vV Lthw==
X-Gm-Message-State: ALoCoQnA+tct8W+8tI45o5PBCT/R5kRvIyuwXzOErFFsHZM0OMNpix8l2W6tjMKTEyWzs0/Z7vd8
X-Received: by 10.112.158.66 with SMTP id ws2mr6277403lbb.126.1449161051423; Thu, 03 Dec 2015 08:44:11 -0800 (PST)
Received: from [192.168.1.103] ([41.232.113.177]) by smtp.gmail.com with ESMTPSA id r2sm1560153lfe.28.2015.12.03.08.44.07 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 03 Dec 2015 08:44:09 -0800 (PST)
Message-ID: <56607154.60001@azet.org>
Date: Thu, 03 Dec 2015 17:44:04 +0100
From: Aaron Zauner <azet@azet.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Jacob Appelbaum <jacob@appelbaum.net>
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> <CANBOYLXJX_gjuC8Rp0Z9YqzNYsbr0x1WeL4AeRUxFtMaM+U5wQ@mail.gmail.com> <CAFggDF2fbpFkURZtjuKc5NWGRdYra+A9gPD6881nk-Crs2ijXA@mail.gmail.com> <5660405E.3060008@azet.org> <56604CAF.5000305@azet.org> <CAFggDF0vsZfH-3=Fsb24dc_TZchZ63jAp=p+LpZcf_UYqjZZcw@mail.gmail.com> <56606CF8.7070505@azet.org>
In-Reply-To: <56606CF8.7070505@azet.org>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="------------enigFC5D092F3A4A65200E75A7F0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/b5kN9yx72Deg6WTQFFUQRxhwYt4>
Cc: "tls@ietf.org" <tls@ietf.org>
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
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 16:44:14 -0000

Errata:

Aaron Zauner wrote:
> BTW, I played with SNI DoS a few months back (not too much though as it
> wasn't worth a paper), seems not to be as bad as it used to be because
> implementations nowadays have at least some counter-measures.

Was supposed to say 'renegotiation DoS' I've looked at SNI as well in
this context.

Aaron

v2.14.0 | Report a Bug | By Email