Extreme example, but code execution is code execution.
I'd hope that PHRACK readers would be among those better prepared for such attacks, but case in point, lack of transport encryption for web traffic is ABSOLUTELY a security issue too, not just a privacy issue.
Not every web site needs HTTPS.
It matters not at all if some government sees me checking the weather, or reading about the best seeds to plant this time of year.
And 99 44/100% of the MITM hype is pure theoretical hysteria. There is a very long distance between "could" and "will" and "can" and "did."
I know a lot of people enjoy their paranoia fantasies. But real life isn't a Tom Cruise movie.
Every site does. HTTPS should be the default, that increases security even if you're just looking at cat pictures in a given context.
> It matters not at all if some government sees me checking the weather, or reading about the best seeds to plant this time of year.
Absolutely does. Much can be deduced from your activity, like whether you're home, what your interests are, who you talk to, what skills you have. If somebody gets poisoned, then your interest in botany might suddenly make you of interest.
For the most part nobody really wants to read your boring emails. But that you regularly talk to some controversial person, or spend a lot of time in their proximity, that's juicy information that may well paint a target on your back in the wrong circumstances.
> And 99 44/100% of the MITM hype is pure theoretical hysteria. There is a very long distance between "could" and "will" and "can" and "did."
Good news: it absolutely happens. MITM has been used for injecting ads in content, which of course can be used to nefarious effect. From just unethical, like replacing a site's original ads with your own and robbing them of the income, to actually malicious payloads.
Your ISP and mobile carriers are not trustworthy neutral carriers of data. Encrypted transports are the only way for end users to avoid their snooping and injection.
Note: this is NOT an endorsement of Chrome, FF, Webkit, Blink, Gecko, nor is it a suggestion to NOT use Lynx - just a reminder that there are no silver bullets in security.
While I agree in principal, in practice https is not very resilient to the attacks you mentioned because CAs are demonstrably [1,2,3] not trustworthy despite being baked into your browser.
1: https://en.m.wikipedia.org/wiki/DigiNotar
2: https://therecord.media/mongolian-certificate-authority-hack...
3: https://arstechnica.com/information-technology/2022/11/state...