3 ms·
What I don't like about the whole HTTPS everywhere initiative is that it makes it even harder to monitor what data is traveling to and from your own PC. In cas
by xg15 10y ago
What I don't like about the whole HTTPS everywhere initiative is that it makes it even harder to monitor what data is traveling to and from your own PC.
In case of browsers, it's luckily still only a theoretical concern today, thanks to the "custom root cert" loophole which practically works like a permission system for monitoring tools. However, I think the conceptual change is important:
With HTTP, the abillity to monitor your own connections is a simple technical consequence. With HTTPS, its a feature that browsers explicitely have to implement and that's potentially subject to all kinds of tradeoffs and political descisions.
I fear that once HTTPS is actually the norm, there will be a number of strong forces to have the loophope removed and make HTTPS connections effectively opaque to everyone but the website operators.
Of course HTTP is no long-term solution as the security risks are real. But you could get rid of most of the risks by focusing on ensuring message integrity while keeping connections transparent. Instead we get an all-or-nothing solution where a connection has to be integrity checked AND encrypted to be considered "secure" by browsers.
- extra88 10y agoI'm not concerned about that happening. I think EMEs being used for not just video but entire page content is a more likely risk.