encrypted_client_hello client extension on FQDN that does not support it

[Haga R.]

Hi!

I'm working on a simple tool to reproduce some JA3 Fingerprint of several client, including , of course, Chromium based browsers. 

With the latest Chromium version (Google 131), I noticed that, when establishing TLS connection, chromium still send the encrypted_client_hello extension despite the target server not supporting it. What ECH key is Chromium using to create this payload? Sorry if I missed something obvious.

Thanks for your time. 

Regards,

Hag

[Daniel Bratell]

I think people on net-dev are more likely to know. Adding it as receipient and setting blink-dev as bcc.

/Daniel

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/86343a33-89eb-4880-ab9a-9233351bffc4n%40chromium.org.