5 ms·
> HTTPS doesn't protect the content of your site from being stolen, it protects your users from hostile third-party content masquerading as yours. Hostile thir
by yardstick 8y ago
> HTTPS doesn't protect the content of your site from being stolen, it protects your users from hostile third-party content masquerading as yours.
Hostile third party content is only hostile because the client used to access the content does not take client security seriously.
Food for thought: As an end user consumer visiting random, benign websites, I want my browser to be protecting me against hostiles, rather than relying on website operators to do that for me. Just like I run antivirus on my machines instead of relying on everyone else to run it.
- chopin 8y agoJust make it so that your browser doesn't render any http delivered content. Problem solved. From a client point of view that's the only protection you can do. A MITM over http is undetectable for you. With current OSes and hardware there is no sandboxing which will protect you under all circumstances. If you do this, site providers are forced to switch to https anyway.
- dragonwriter 8y ago> If you do this, site providers are forced to switch to https anyway. No, if everyone does this, providers are forced to switch. If you do it, it just means you're cut off from some portion of the web.