IETF Logo Mail Archive

[TLS]Re: [EXTERNAL] Adoption call for SSLKEYLOG Extension file for ECH

hannes.tschofenig@gmx.net Sat, 03 August 2024 16:36 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 A4F75C14F6EF; Sat, 3 Aug 2024 09:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S_G0b8o4uB7M; Sat, 3 Aug 2024 09:36:20 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EF3BC14F605; Sat, 3 Aug 2024 09:36:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.net; s=s31663417; t=1722702978; x=1723307778; i=hannes.tschofenig@gmx.net; bh=q30e4aSRm8HQKmSzhBwwCh6xGdw5xiuMVMoJZ2H0Ui4=; h=X-UI-Sender-Class:From:To:References:In-Reply-To:Subject:Date: Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:cc: content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=gdKAA30uQ1vVoe/P4glJnNR53/16LPbwv9MVASvOBTUlGXu2bRp0WHQ39gs4lCj/ Tz3BcHkJCbcYadB4wAcnQGGdYnjaDLeRM9K+TdFSxX3DcDvZ0uXO7ccUGdcG24gme /g8QLGJlIKwNVtyGjiC9r7hfrWTiwj28XDdSNeUNlKXCJZCruRzgEgGhzklqCLpNB U3snv/j6MFFFv68VDy69El0V0kiRMkovLW+4BI8adY3knHZQ8nWdgteZqgwvF5ScG lafctygztbctOFO6PWd1o7NC2SaApAKUM8t/GFg9BbQWOF0aVeoZp3nA3evYX8nht YpV0+q5msFOZfxI3GQ==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from Surface ([185.176.157.173]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MzhnN-1sNPgu3GVd-011Ejr; Sat, 03 Aug 2024 18:36:17 +0200
From: hannes.tschofenig@gmx.net
To: 'Andrei Popov' <Andrei.Popov=40microsoft.com@dmarc.ietf.org>, 'Sean Turner' <sean@sn3rd.com>, 'TLS List' <tls@ietf.org>
References: <7CC88431-A71A-455B-A7A7-BA4AD3C8502C@sn3rd.com> <MN0PR21MB3147C2C3EE7B9115F339ADDE8CAB2@MN0PR21MB3147.namprd21.prod.outlook.com>
In-Reply-To: <MN0PR21MB3147C2C3EE7B9115F339ADDE8CAB2@MN0PR21MB3147.namprd21.prod.outlook.com>
Date: Sat, 03 Aug 2024 18:36:16 +0200
Message-ID: <029901dae5c3$437addc0$ca709940$@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: de-at
Thread-Index: AQMlFNuwYsvybUUT16I2Y7Ht+kD1/AFwfNZqr3XXeQA=
X-Provags-ID: V03:K1:dr8zmT/Z/GiqyOfWppE7ysMd6DYZJ9j2TuOcfQGP/WHEf6k6N+0 Y57YwS8V2Awm8g57phGi7SUUU/K9yXu9QNy6/hyYrq0dOPhHGsqwwKMA5lOkrdIbYPEcfvn WMTE1WnBjVZGUDMyQgR6BX9F0WgIYqmx83qGvqIeGr6SRxVrVj8v3sIPCzgtbXQVK6TMPRg RknNYqEQF/GgL2ZwiRSuw==
UI-OutboundReport: notjunk:1;M01:P0:MfDP132RgCI=;7hTrenvB/veCutbOHGHl/XgR2xG 8wcIpGx0HkFtOx/9dywDKmuKw/34LbTNycQWBLZa5Qklpv3xjLw+Bzmlu1TNFhwG3LikjSjfD iQKLPZ9xsr/7QLStKgDHnYgjQHcVWeGNXTkNUsnnKmhWys8vINA4ISrcBFt0DyL+7URsAsFU7 T6wgu+d39+8MEOjQj7EDtqLmuWKTSH0JbkYDiXRyhaIUvuPr0kZGY0q9qgFVOANXu2ksAjmcb b+AIUIITYXoH2q484RmqD3J/yiKdEcALQHQ7lfsUMSQtSVwH3ZGfUNOpUyMdQvPVhI7+MswcC p0WiRSsv5Fa31WAUSJ/KTstH4wbmR7M0FtQf9Zq9PiHIQ8nqALsGrO5T/wl632XnXe/BUSDwI eTpw0RBTfDNN74NtjfBXWCcaCD6UINBWcW/XxJeB/IxZG/wQZ0vRzdlN5WsOMLSRto/nXBv/2 CUmwfNPOvZcorNNDaAI0WhrCwCs1DFg30YGMENn51tHU3wPsFnSjzYhdR4i2sVxFdla/9guE8 LZGukDGVXc8eSgEU1JihJOS5HDT7VrsScoDcCtz3gqLSFrsZYidCHpHuvpZ+U1W0X1Jo6J9oI 5+sqZ+1iayV6cpUrXzrjDxAGiHPZx4AoknTC84hruHFqX1vk0uILsQmIIsEDaKB1jk8j+QNa8 hCI+eph3K7jaMnjrMaBNEXtp3nhsNzCEx63mLtI31GQIJBiBBqA01D0jViY6RXCLBba2G83uq GBt9I2QHi7QIXyuU9RNAeErJPpBKIuJcIHSYxDjL73L9Lmq0yHccfDpue27UpKUtwbrcUi9qv 39ODYaCaWwS/6yDKrSz/pFgOhtpj3tpEW8ZTCozKHRR8A=
Message-ID-Hash: VXNMDYT4MFULXDBHPH2HCVFOUAZYF7M4
X-Message-ID-Hash: VXNMDYT4MFULXDBHPH2HCVFOUAZYF7M4
X-MailFrom: hannes.tschofenig@gmx.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [TLS]Re: [EXTERNAL] Adoption call for SSLKEYLOG Extension file for ECH
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/NUZIhMRlsSO9ul27jakWI9xuR5A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

Hi Andrei,

as a developer you rely on ways to decrypt traffic for debugging purposes. The draft does not define a new mechanism but instead relies on and extends an already existing TLS working group item, see https://datatracker.ietf.org/doc/draft-ietf-tls-keylogfile/
Hence, this is not a mechanism that allows a third party in the middle of the network communication to somehow decrypt traffic. It is a tool for a developer and must be enabled by the developer on one of the involved end points to work.

Publishing the draft as informational, much like draft-ietf-tls-keylogfile is, sounds good to me though.

Ciao
Hannes

-----Original Message-----
From: Andrei Popov <Andrei.Popov=40microsoft.com@dmarc.ietf.org> 
Sent: Donnerstag, 25. Juli 2024 18:30
To: Sean Turner <sean@sn3rd.com>; TLS List <tls@ietf.org>
Subject: [TLS]Re: [EXTERNAL] Adoption call for SSLKEYLOG Extension file for ECH

I do not support adoption, because I believe the IETF should not standardize tools and techniques for decrypting TLS-protected data.
It is harder for a TLS implementer to reject requests for IETF-blessed functionality.

(As long as this remains on the Informational track, I believe it's somewhat less harmful.)

Cheers,

Andrei

-----Original Message-----
From: Sean Turner <sean@sn3rd.com>
Sent: Thursday, July 25, 2024 9:16 AM
To: TLS List <tls@ietf.org>
Subject: [EXTERNAL] [TLS]Adoption call for SSLKEYLOG Extension file for ECH

At the IETF 120 TLS session there was interest in adopting the SSLKEYLOG Extension file for ECH I-D (https://datatracker.ietf.org/doc/draft-rosomakho-tls-ech-keylogfile/) This message starts a two-weekl call for adoption. If you support adoption and are willing to review and contribute text, please send a message to the list. If you do not support adoption of this I-D, please send a message to the list and indicate why. This call will close on 8 August 2024.

Thanks,
Sean
_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-leave@ietf.org

_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-leave@ietf.org

v2.26.15 | Report a Bug | By Email | System Status