From stephen.farrell at cs.tcd.ie Wed Apr 3 10:15:50 2024 From: stephen.farrell at cs.tcd.ie (Stephen Farrell) Date: Wed, 3 Apr 2024 11:15:50 +0100 Subject: [ech] Fwd: [TLS] Working Group Last Call for ECH In-Reply-To: <2a07c2cb-363e-40dc-b487-82155ed1d5ae@cs.tcd.ie> References: <2a07c2cb-363e-40dc-b487-82155ed1d5ae@cs.tcd.ie> Message-ID: <994c7aaa-7760-4d0a-9595-c5677282e4a2@cs.tcd.ie> Hiya, FYI: The ECH spec has now finished working group last call in the IETF TLS WG [1] so will likely become an RFC with no substantive change in a few months. I'd really love to chat about how to progress my ECH PR [2] with the goal of being able to merge ECH stuff not too long after the RFC issues... Cheers, S. [1] https://mailarchive.ietf.org/arch/msg/tls/PYohY5ND75ixDqupTY6bgNgitMY/ [2] https://github.com/openssl/openssl/pull/22938 On 11/03/2024 22:41, Stephen Farrell wrote: > > Hiya, > > FYI: as always, slower than hoped for, but the ECH spec > has taken another step towards being an RFC just now. > > If anyone on here hasn't read the thing before and has > an interest, now would be a great time to get a new set > of interested eyeballs on the text. > > Cheers, > S. > > PS: I hope this also motivates someone to do a bit of > review of my ECH PR;-) > > -------- Forwarded Message -------- > Subject: [TLS] Working Group Last Call for ECH > Date: Mon, 11 Mar 2024 15:00:01 -0700 > From: Joseph Salowey > To: > > This is the working group last call for TLS Encrypted Client Hello [1]. > Please indicate if you think the draft is ready to progress to the IESG and > send any comments to the list by 31 March 2024.? The comments sent by > Watson Ladd to the list [2] on 17 February 2024 will be considered last > call comments. > > Thanks, > > Joe, Deirdre, and Sean > > [1] https://datatracker.ietf.org/doc/draft-ietf-tls-esni/ > [2] https://mailarchive.ietf.org/arch/msg/tls/XUCFuNBSQfSJclkhLW-14DZ0ETg/ > > -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0xE4D8E9F997A833DD.asc Type: application/pgp-keys Size: 1197 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 236 bytes Desc: OpenPGP digital signature URL: From stephen.farrell at cs.tcd.ie Tue Apr 16 11:34:21 2024 From: stephen.farrell at cs.tcd.ie (Stephen Farrell) Date: Tue, 16 Apr 2024 12:34:21 +0100 Subject: [ech] ECH added to curl as experimental feature Message-ID: <7c0c74c0-087b-4c19-9d41-6910ca8495f9@cs.tcd.ie> Hiya, An ECH PR [1] we wrote has just been merged with curl as an experimental feature. (For curl that means it's not built by default, but adding ``--enable-ech`` to a local build enables it.) (Unsurprisingly:-) That PR supports our ECH additions to OpenSSL, but we also added ECH support to curl via other TLS stacks (boringssl and wolfssl) that include ECH already. In other news, we've also now got a daily CI check of our various ECH artefacts that can be seen at [2]. In the case of OpenSSL, that job attempts to merge our fork with upstream master and runs tests each day and we get to see fails as they happen. (And fix 'em a day or two later:-) All of which is meant to further encourage people to pretty please do some review of our ECH PR [3] as now is a great time to make inroads on that before the ECH RFC issues and other code bases move ahead. Cheers, S. [1] https://github.com/curl/curl/pull/11922 [2] https://github.com/defo-project [3] https://github.com/openssl/openssl/pull/22938 -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0xE4D8E9F997A833DD.asc Type: application/pgp-keys Size: 1197 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 236 bytes Desc: OpenPGP digital signature URL: