From nobody Tue Jun 15 13:34:39 2021 Return-Path: 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 A98913A3CF5 for ; Tue, 15 Jun 2021 13:34:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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=cloudflare.com 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 2jbMhWV9po_f for ; Tue, 15 Jun 2021 13:34:34 -0700 (PDT) Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 844753A3CF4 for ; Tue, 15 Jun 2021 13:34:34 -0700 (PDT) Received: by mail-qk1-x729.google.com with SMTP id c9so358954qkm.0 for ; Tue, 15 Jun 2021 13:34:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2bPleIYqfojO3o5LFpfksiISaRuccF66cXJqAWG8Lio=; b=i8wAVRakjau68tK3Eh9tRAeUtRKlei4kbnxlrZFy/fEVSyAtzGrE4o7fenGSmduymw pdm8C8tOeVrgIFgjUcS9t9ag/CI0UcHbZ8Qz3i968b3xHYGM2586BjLws4arakd4EZ4T dkp8liIVyFPfW8d1NiUtSMyKLAvb8ulnzbDSc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2bPleIYqfojO3o5LFpfksiISaRuccF66cXJqAWG8Lio=; b=paw6uRWyfvX/h+czg2NuCX6aFr0LY5VC4NReMuMAXWS4S5IllrHURA7klxaCmH4U6p FmtDY/Pn/pavQTR8qAV9Ne7R8m1gN0GAsxrEnIhG5ER/cH2wTURG22FTXH9BqtujL0Hx UY0t4zjhK2vijephnMNc9S3934tXPyoqIjSkavpUCG4Ru1IKTO4tZFw+mLGRg9ov8gx+ r1GiVJsCRQRrZNYmrXA9g3/YVfauYuvSRrv/59S7qgJlgu/pPfLYU841g3MPHcrsVqE2 oPSYaC3Uc/nwMk6YoGSE6n2GLFEnwsaTiZvzBFATsyoktsgLD1AnMniO8yuvhirm4fxi ISeQ== X-Gm-Message-State: AOAM53163ahBsjR+qsDdAQAMQZvhQ+U5XtNFwNyIwCDC6eKpVZ37PLtT A8JG0Puefmr3W9eqsKHETjyaO2s8NFY3snbs20GtQA== X-Google-Smtp-Source: ABdhPJzjMYebv2xyN7jP3/i30JN/Yj+iy7lmQMtT82mnJvgYRT+SjfC//IuIqusRij5If68XWjtnFndDA4Pr8l1DmQM= X-Received: by 2002:a37:e106:: with SMTP id c6mr1478472qkm.338.1623789273482; Tue, 15 Jun 2021 13:34:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Christopher Patton Date: Tue, 15 Jun 2021 13:34:22 -0700 Message-ID: To: Rob Sayre Cc: "" Content-Type: multipart/alternative; boundary="000000000000d62bc905c4d3e6a5" Archived-At: Subject: Re: [TLS] ECH-10 interop test server X-BeenThere: tls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2021 20:34:39 -0000 --000000000000d62bc905c4d3e6a5 Content-Type: text/plain; charset="UTF-8" Hi Rob, today we're currently rolling out an update to crypto.cloudflare.com that disables support for P-384 and P-521. This should allow you to easily trigger HRR. Chris P. On Mon, Jun 7, 2021 at 9:24 AM Christopher Patton wrote: > Hi Rob, let me look into it. > > Chris P. > > On Fri, May 28, 2021 at 11:36 AM Rob Sayre wrote: > >> On Mon, Apr 5, 2021 at 10:02 AM Christopher Patton > 40cloudflare.com@dmarc.ietf.org> wrote: >> >>> Hi list, just FYI that Cloudflare's test server is upgrading to >>> draft-ietf-tls-esni-10 this morning. It should finish rolling out in a few >>> hours. Note that we've dropped support for draft-ietf-tls-esni-09. >>> >>> The endpoint is https://crypto.cloudflare.com. You'll also find our ECH >>> config in the HTTPS resource record. >>> >> >> I've gotten a Rustls client to interoperate with this server, but I had >> some trouble triggering HRR, since Rustls always sends a key-exchange group >> in TLS 1.3. I managed to hack up a ClientHello and handshake with no >> initial key-exchange group, but perhaps it could be easier. >> >> It might be nice to have this server reject secp384r1 and offer X25519 in >> an HRR, or something like that. >> >> thanks, >> Rob >> >> --000000000000d62bc905c4d3e6a5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Rob, today we're currently rolling out an upda= te to crypto.clo= udflare.com that disables support for P-384 and P-521. This should allo= w you to easily trigger HRR.

Chris P.

On = Mon, Jun 7, 2021 at 9:24 AM Christopher Patton <cpatton@cloudflare.com> wrote:
=
Hi Rob, let me look into it.

Chris P.

On Fri, May 28, 2021 at 11:36 AM Rob Sayre <sayrer@gmail.com> wrote:
On Mon, Apr 5, 2021 at 10:02 AM Christ= opher Patton <cpatton=3D40cloudflare.com@dmarc.ietf.org> wrote:
Hi list, just FYI that Cloudflare's test serv= er is upgrading to draft-ietf-tls-esni-10 this morning. It should finish ro= lling out in a few hours. Note that we've dropped support for draft-iet= f-tls-esni-09.

The endpoint is https://crypto.cloudflare.com.= You'll also find our ECH config in the HTTPS resource record.

I've gotten a Rustls client to inte= roperate with this server, but I had some trouble triggering HRR, since Rus= tls always sends a key-exchange group in TLS 1.3. I managed to hack up a Cl= ientHello and handshake with no initial key-exchange group, but perhaps it = could be easier.

It might be nice to have this ser= ver reject=C2=A0secp384r1 and offer=C2=A0X25519 in an HRR, or something lik= e that.

thanks,
Rob

=
--000000000000d62bc905c4d3e6a5--