Re: [TLS] Draft RHRD

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 01 November 2017 14:24 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 515AB13FC00 for <tls@ietfa.amsl.com>; Wed, 1 Nov 2017 07:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 r4nFf28irXij for <tls@ietfa.amsl.com>; Wed, 1 Nov 2017 07:24:37 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AAAD13FBE8 for <tls@ietf.org>; Wed, 1 Nov 2017 07:24:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id BB12FBE50; Wed, 1 Nov 2017 14:24:34 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAuisWEbT5Ei; Wed, 1 Nov 2017 14:24:34 +0000 (GMT)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 64401BE3E; Wed, 1 Nov 2017 14:24:34 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1509546274; bh=h8FULmKCPWI/9Rp+a2xVVJp0Y5kvphI3aIGM/6/r3wc=; h=Subject:To:References:From:Date:In-Reply-To:From; b=YWd4RL8WGpSOUVh8WpHPRbJpAnWVPKrfRFm6F+SoguLywSBE5eS+u1y96J14jtvXP Xh/m7Zn2cyEf0mi23H/rA4Tq7Kqi7GT6JpOpd/v+J/W2EyxbtwOLOZ/xH/57751FeM QC6GRS8XIIrj1c+qCdobBJwP3LXiX+B64PHO3ORw=
To: "Salz, Rich" <rsalz@akamai.com>, "tls@ietf.org" <tls@ietf.org>
References: <C2DD7992-0A5A-4970-8DDB-DBA651B4D6D7@akamai.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <e1c9b73f-97b5-f604-c7bc-1014479f9fd7@cs.tcd.ie>
Date: Wed, 01 Nov 2017 14:24:33 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <C2DD7992-0A5A-4970-8DDB-DBA651B4D6D7@akamai.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="GdeuDFG0Lv9QBxcbA8GJdbcrdijbBb92p"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/6B6jm7FYGykld0JbzeX9fBM2r5k>
Subject: Re: [TLS] Draft RHRD
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 01 Nov 2017 14:24:39 -0000


On 01/11/17 14:18, Salz, Rich wrote:
> In https://www.ietf.org/mail-archive/web/tls/current/msg24789.html,
> Nick Sullivan concluded:
> 
>> - on the other hand using draft-rhrd is safer than allowing
>> organizations to hack single-key escrow into TLS 1.3 or continue to
>> use TLS 1.2 with non-forward-secret cipher suites
> 
> I think this sets up a false comparison.  Existing TLS 1.3 debugging
> systems – Wireshark – can debug individual TLS sessions with the
> session key information being made available.  This is what the RHRD
> draft would require an organization to do, but it adds the additional
> signaling that the client is willing to allow it. The Wireshark
> example shows that the signaling is not needed.  Servers can
> unilaterally do it now.
> 
> I maintain that the cleartext signal servers no useful purpose,
> except to provide a mechanism for entities to segregate traffic.

I agree. I'd also like to point out that that in no
way implies that the absence of the visible signal
is any better. As we saw with draft-green, it was not.

S.

> 
> 
> 
> _______________________________________________ TLS mailing list 
> TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
>