I know Chrome had to implement a race between tcp and quic to detect various forms of broken firewalls, content filtering devices, etc. Maybe it would be better just to let things break and force the issue?
I know Chrome had to implement a race between tcp and quic to detect various forms of broken firewalls, content filtering devices, etc. Maybe it would be better just to let things break and force the issue?
If you can't inpect --- and alter --- what your devices are sending and receiving, it's not yours.
Big Tech seems to be on a race to own the Internet through increasing complexity and "upgrade treadmilling", and I block everything except HTTP 1.1 and 1.0 as a form of protest.
I've always found it ironic that a lot of the anti-MITM-proxy folks are the same ones who work at or approve of the companies which are bringing more pervasive-surveillance "smart" devices to the market, locking down end-user-devices against the user, or trying to get you to consume more of their ads. Everything they say they do is for "security" and "privacy". They obviously don't want you getting in the way. Coincidence or not? You decide...
I think it would be better, but unfortunately it won't happen. Too much money riding on it. I still hope newer versions of http continue to be designed to be more resistant against these garbage tools.
What are we missing out on, because of the refusal to let go of pointless legacy systems?
Well, ECH instead of eSNI now, but yes, I would have loved this. Since browsers are all going to be willing to fall back to sending the website name in cleartext, anyone evil enough to be willing to do censorship or surveillance will just block eSNI and ECH.