Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

esni (encrypted sni) does not work anymore

  • 3 Antworten
  • 1 hat dieses Problem
  • 1 Aufruf
  • Letzte Antwort von cor-el

more options

In the past I used to be able to turn encrypted sni on I did a firefox reset yesterday then I reinstalled my add ons

and I re-enabled encrypted sni by setting: about:config network.security.esni.enabled = true

but when I test it on https://www.cloudflare.com/ssl/encrypted-sni/ the test takes a lot longer and also everything is green except esni: "Your browser did not encrypt the SNI when visiting this page."

So something is clearly wrong, but I don't know what it is.

how do I fix this?

In the past I used to be able to turn encrypted sni on I did a firefox reset yesterday then I reinstalled my add ons and I re-enabled encrypted sni by setting: about:config network.security.esni.enabled = true but when I test it on https://www.cloudflare.com/ssl/encrypted-sni/ the test takes a lot longer and also everything is green except esni: "Your browser did not encrypt the SNI when visiting this page." So something is clearly wrong, but I don't know what it is. how do I fix this?
Angefügte Screenshots

Alle Antworten (3)

more options

Hi, the plan is to switch from ESNI to ECH (Encrypted Client Hello).

  • Bug 1667801 - Cloudflare reports ESNI is no longer working (ECH)

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)


Comment 14:

I'd like to update our current plan about esni and echConfig. That is we will only support echConfig in the future. esni is supported now, but will be replaced by echConfig when bug 1654332 is done.

Geändert am von cor-el

more options

Thanks for your answer, but things remain unclear for me.

"

cor-el said

the plan is to switch from ESNI to ECH (Encrypted Client Hello).

First question: this answer implies that encrypted sni should still be working, is the bug only causing problems for me or does everybody with firefox 84.0.2 have the same issue? and why is it still configurable in about:config if esni support is gone?

Second question: Should I switch to ECH (Encrypted Client Hello)? Is it the same as encrypted sni?

Should I turn network.dns.echconfig.enabled = true? (It's still false in my default config)

sorry for many the questions, thank you in advance.

more options

Geändert am von cor-el