User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:85.0) Gecko/20100101 Firefox/85.0

Steps to reproduce:

network.trr.mode = 3
network.security.esni.enabled = true
network.trr.uri = https://dns.adguard.com/dns-query
network.trr.bootstrapAddress = 94.140.14.14

That bug occurred after the update. And after de-setting and resetting, I repeated the restart several times.

Actual results:

Cloudflare: Your browser did not encrypt the SNI when visiting this page.

And you can't bypass sni censorship in Korea.

Expected results:

Cloudflare: Your browser encrypt the SNI when visiting this page.

And you can bypass sni censorship in Korea.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

I want bypass SNI censorship. why I can't bypass this?

ESNI is superseded by ECH. We can do nothing about that until the server is updated to support ECH.

(In reply to Masatoshi Kimura [:emk] from comment #9)

ESNI is superseded by ECH. We can do nothing about that until the server is updated to support ECH.

ok, I got it. In summary, can I understand that ESNI cannot work until the server(such as using Cloudflare service server) supports ECH?

(In reply to Masatoshi Kimura [:emk] from comment #9)

ESNI is superseded by ECH. We can do nothing about that until the server is updated to support ECH.

Is there any reasonable explanation why Mozilla removed ESNI before the arrival of working alternative? You cannot just refer to bad Cloudflare and others that are yet to support ECH. ESNI was working and the service is still provided by Cloudflare. Many people relied on it to improve their privacy.

Why Mozilla endangered privacy of those users without even a heads-up?