Those two links have ruined my life, seriously, i can no longer access expensive to replace, but otherwise perfectly working hardware on my own local private network using FF since the ridulous decision to remove TLS 1.* entirely.
I'm not the only one. Many of us are having issues with devices we can no longer access and configure from the browser. The management facilities on switches, ilo,servers, printers.. etc that are working perfectly well.
@2Big4YourBoots - can't access their own router!
.For me, i have old, but extremely expensive server hardware that is unable to be replaced for finanical reasons (i dont have work due to disability).
. Also a printer Management module can no longer be accessed.
.I don't run any kind of business with my two servers, purely storage and hobby, and rarely used on internet except for windows updates.
.But accessing them via ILO3 (which only supports tls1.0 and tls 1.1) and no longer possible via browser.
.This makes powering them up, shutting them down and monitoring hardware/health remotely impossible for me, and physically painful.
.HP will not update ILO3 to support tls1.2. ILO3 cannot be upgraded or updated to iLO4.
.i suggest the Moz implement a "DMZ" for local network (and same subnet hardware), where FORCED, (for the so called "benefit of users") rules are able to turned off.
.Maybe firefox could generate it's own safety cert/exclusion key - which is emailed to the users verified email address for specific trusted hardware on a local network, as in my example.
EVERYONE .Please do advise if there are known working fixes, workarounds, add-ons, software etc for accessing my own hardware with TLS 1.0