2 ms·
This is true, however the current push to enforce HTTPS everywhere normalizes encrypted traffic. If encrypted or obfuscated connections were rare, you could mak
by xg15 5y ago
This is true, however the current push to enforce HTTPS everywhere normalizes encrypted traffic. If encrypted or obfuscated connections were rare, you could make a filter that only lets through inspectable connections and deploy it without much breakage. If all connections are encrypted, you cannot distinguish between safe and suspicious traffic at all.
Together with eSNI, DoH and QUIC, the goal is pretty explicitly to treat the network as an adversary. That's a good thing if you really don't trust the network but a bad thing if you lose control over your own network.
- zamadatix 5y agoAgain, you can inspect or easily get the decryption keys traffic on devices you control such as your PC or your Web Browser. If you control the OS but not the applications you choose to run set up an explicit proxy and inspect there. If the app doesn't follow explicit system proxies add your transparent proxy key to the root store. If the app ignores that then congratulations, you're at "you could make a filter that only lets through inspectable connections and deploy it without much breakage" without getting rid of the benefits of Encryption to do so. Encryption is not what makes the app communication opaque, inability to control the device does. The external network IS an adversary when it comes to your data. If you truly controlled your data at the start then you can specify where the external network begins. By default that is when it leaves your PC but it does not always have to be that point.