Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

How to stop Firefox from sending TLS 1.0 even after disabled in settings.

  • 4 wótegrona
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót Mike Leimer

Mike Leimer
Mike Leimer
more options

Currently running Firefox 73.0.1.

Connections to my server from Firefox all fail with 'connection_reset' from the server.

Wireshark capture shows that Firefox is attempting a 'Client Hello' using TLS 1.0.

Servers are configured with TLS 1.0 removed/disabled.

All the Firefox advanced settings in about:config are set with TLS 1.2 as the minimum, yet Firefox insists on sending TLS 1.0 'client hello'.

Not an expert, but it kind of looks like Firefox is sending a TLS 1.2 'Client Hello' encapsulated inside a TLS 1.0 'Client Hello'? Is this even possible?

Chrome, IE, and Edge behave appropriately and send 'Client Hello' as TLS 1.2.

How do we get Firefox to send the appropriate 'Client Hello'?

This affects multiple versions of Firefox, even the beta builds that I tested over the weekend and occurs on any machine tested so far. Windows 10, various flavors of Linux, etc.

See screenshots below for configuration settings and wireshark capture.

Thanks for the help!

Currently running Firefox 73.0.1. Connections to my server from Firefox all fail with 'connection_reset' from the server. Wireshark capture shows that Firefox is attempting a 'Client Hello' using TLS 1.0. Servers are configured with TLS 1.0 removed/disabled. All the Firefox advanced settings in about:config are set with TLS 1.2 as the minimum, yet Firefox insists on sending TLS 1.0 'client hello'. Not an expert, but it kind of looks like Firefox is sending a TLS 1.2 'Client Hello' encapsulated inside a TLS 1.0 'Client Hello'? Is this even possible? Chrome, IE, and Edge behave appropriately and send 'Client Hello' as TLS 1.2. How do we get Firefox to send the appropriate 'Client Hello'? This affects multiple versions of Firefox, even the beta builds that I tested over the weekend and occurs on any machine tested so far. Windows 10, various flavors of Linux, etc. See screenshots below for configuration settings and wireshark capture. Thanks for the help!
Pśipowjesone fota wobrazowki

Wšykne wótegrona (4)

TyDraniu
TyDraniu
  • Top 10 Contributor
more options

What about security.tls.hello_downgrade_check?

Mike Leimer
Mike Leimer Pšašaŕ
more options

Thank you for the help!

When I attempted the connection earlier, security.tls.hello_downgrade_check was set to the default of 'true'.

I changed security.tls.hello_downgrade_check to be 'false', went to 'Preferences | Privacy & Security | Cookies and Site Data' and cleared all data. Then I closed the browser and rebooted the VM.

Still I get a TLS1.0 'Client Hello' just as before.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
more options

Mike Leimer said

Then I closed the browser and rebooted the VM.

Is there anything in the VM that might be proxying the connection from Firefox?

Mike Leimer
Mike Leimer Pšašaŕ
more options

Sorry for the added confusion there, nothing is set up to proxy the VM, networking is set up to NAT my workstation network connection.

Additionally, I see the same behavior on any of the physical machines that I have tested on as well.

I have just been using a VM on my workstation for convenience and to grab the screenshots for this post, but the behavior is identical to physical PC's in this context.

  • As an interesting note, during this troubleshooting I did install Fiddler on one of the physical workstations.

Using Fiddler as a proxy, the Wireshark capture *does* show a TLS1.2 'Client Hello' and the connections to my website *does* complete successfully, so it appears that Fiddler is sending the appropriate TLS1.2 request on behalf of Firefox. I'm not sure if this means anything, or nothing but I thought I'd share it as a data point.