4 ms·
The intuitive properties you expect from HTTP actually aren't delivered and can't be delivered, except over HTTPS. A lot of people focus on the confidentiality
by tialaramex 5y ago
The intuitive properties you expect from HTTP actually aren't delivered and can't be delivered, except over HTTPS.
A lot of people focus on the confidentiality element of TLS. "Clearly I don't need for it to be secret that I looked at the Wikipedia entry for Napoleon (the 1995 movie, not the famous guy)".
But TLS bundles together three things and if you need any of them you can't have them with plain HTTP. You get confidentiality, but you also get integrity and authentication.
That means when you curl https://foo.example/something https://foo.example/something we can promise you that the result is the resource https://foo.example/something https://foo.example/something - maybe that's not what you actually wanted, maybe it's full of lies or worse, but it is what you asked for and it is what you get. With plain HTTP all bets are off, anybody can interpose and present anything else to you.
If it's OK if you just get anything and not the article from Wikipedia, why even look at Wikipedia at all? You could make up whatever you want, it's a black-and-white movie about a dog who ruled France and then went into space, and it was the #1 grossing movie in every country for six years.
- dvfjsdhgfv 5y ago> If it's OK if you just get anything and not the article from Wikipedia, why even look at Wikipedia at all? This is probably the argument I hear most often. But it completely ignores the fact that for the last 20 years, when I wanted to grab a Wikipedia article, I got it in 100% cases, whereas the number of broken HTTPS websites (usually because of expired certs) is non-negligible. You can blame "incompetent admins" as much as you want, but with HTTP this particular problem simply doesn't exist.
- rezonant 5y agoSure, it is incredibly rare for a man-in-the-middle attack to take place at the ISP level in the US. But regular users want WiFi at their favorite coffee shop, and there are still plenty of unsecured wireless hotspots at those shops. The capability to intercept insecure WiFi has been heavily commoditized over the years since the techniques were created. Well within reach for a disgruntled lover, or a stalker, or perhaps for corporate espionage. Sure, more sophisticated organizations should have and more often do have protections for this (including, of course, strong TLS/HTTPS) but not everyone does, and we should protect them too. But that's just in the US, what about in countries where the ISP is far less than trustworthy. It's feasible that a state actor or other malicious actor could replace your web page with a phishing page. A non-sophisticated user (or even a somewhat sophisticated one, if the phishing attack is done well enough) might make that critical mistake that grants access to what is normally highly secured, but because a webmaster who doesn't understand the risks decided not to enable HTTPS, the user's personal information (or worse, their life) could be at risk.
- ArchOversight 5y ago> incredibly rare for a man-in-the-middle attack to take place at the ISP level in the US. Comcast and other ISP's would love to have a word with you with their injecting JavaScript to warn you about going over your alloted data usage... same for various other providers that injected ads, or man in the middled YouTube connections (T-Mobile) to reduce the quality delivered over their network or the hidden CDN's to reduce interconnect load... ISP's have "managed" their networks in a variety of ways, and a lot of those "techniques" were straight up hijacking your original request.
- simfree 5y agoT-Mobile is throttling all traffic from certain IP addresses in their current Binge On scheme, primarily to reduce edge load (on their cell towers) as that is where nearly all of their network congestion occurs. Binge On doesn't do much different for http video content compared to https content as far as I have read and seen.
- ArchOversight 5y agoThese days they may simply throttle entire IP blocks, there was a time when they would purposefully change the manifest file that was served to users to reduce the available qualities thereby forcing the client to think there was no higher quality video content available.
- fnml 5y agoA state actor can issue a certificate, because the browser's default cert stores are full of sketchy ones. The Internet didn't exactly collapse between 1990-2010, before this HTTPS-everywhere campaign started. Interest groups want to get you hooked on HTTPS and then squeeze you, one way or another.
- vegardx 5y agoNo, it doesn't work like that. Certificate Transparency Log makes this almost impossible to do this undetected. In addition to this you have CAA records which quickly would make it evident for the entire world that said certificate is fraudulent and that the signing CA isn't to be trusted anymore.
- NikolaNovak 5y agoI fully agree with the theoretical threat vector. But is it an actual, practical, meaningful threat vector or an issue for the type of website I describe (empathically, NOT top 20 site, like Wikipedia is:)? Everything in IT and IT Security is or should be an evaluation, a compromise of specific graphs of price and effort and impact and risk. My question is not "Should Wikipedia have HTTPS", but "Does every single one of remaining 15% of websites need to be encrypted", and that's not a persuasive argument.
- yakireev 5y ago> But is it an actual, practical, meaningful threat vector or an issue Back when http was common and 3G was still kinda expensive, many public WiFi networks would MITM all the web pages you request to inject their own ads into them. A notable example I remember vividly - the public WiFi network of Moscow Metro used to do this for non-paying customers, and it was particularly bad because 3G/4G did not work well underground back then. This alone was a good motivation to switch my plain-html ad-free websites to https as soon as Let's Encrypt became a thing.
- ChrisArchitect 5y agoVive le roi chien de l'espace!