4 ms·
I have really mixed feelings about deprecating HTTP for HTTPS. There are a lot of websites that are never going to migrate, websites with quality content. There
by marginalia_nu 5y ago
I have really mixed feelings about deprecating HTTP for HTTPS. There are a lot of websites that are never going to migrate, websites with quality content. There's also a lot of clients that are never going to support HTTPS. There's nothing wrong with them otherwise, the hardware is still good, but they can't be used anymore and it's not the owners choice to decide, but a few big tech companies pushing this change.
Even if we do care about these nefarious men in the middle, the elephant in the room is that a large part of the encrypted traffic these days go through major CDNs, and for them to actually pages and and route requests and be anything more than a glorified NAT, they need to inspect what's being sent, and keep track of who is sending it. Even if they totally pinky swear they aren't doing anything nefarious with their position of being able to inspect and analyze a huge portion of the Internet's traffic, and even if we believe them, that can change.
Remember SourceForge? Remember when they were the heroes of open source, the go-to host for source code and binaries? Remember when they were bought up and subsequently were caught with their fingers in the cookie jar bundling malware in said open source packages?
All I'm saying is that there sure is a lot of eggs in that basket. Is a lot easier to lean on one or two CDN operators than it is to lean on every ISP in the country.
- thayne 5y ago> Is a lot easier to lean on one or two CDN operators than it is to lean on every ISP in the country. First of all, that's ignoring how easy it is to MiTM on a public wifi network. Secondly, if a CDN starts misbehaving, customers can switch to a different one. For many people in the US at least if an ISP is misbehaving, there may not be any other option to switch to.
- marginalia_nu 5y agoIt's a matter of scale. You can perform opportunistic small scale mitm attacks on wifi. Maybe that is a concern for interactive websites. But servers that only host static content, why do they need encryption? And how would you find out if a cdn was misbehaving, especially in the context of gag orders? And even if we did find out, it's out in the open that Facebook and Google is doing all this really invasive tracking, yet nobody seems to be leaving them in any hurry.
- chrisan 5y ago> There's also a lot of clients that are never going to support HTTPS What kinds of clients dont support HTTPS?
- marginalia_nu 5y agoHTTPS as a standard has pretty wide support, but the versions of TLS that is increasingly mandatory has much more limited support in older software. There is also a growing problem with stale root certs that are not always possible to update.
- 2Gkashmiri 5y agoi do not understand what is the drama about 100% https adoption? if i am watching videos or reading comics or reading recipes or surfing old books and stuff, why the hell should i be concerned about "privacy" and "mitm" and "end to end" ? i would be personally happy if my payments are secure enough that i pay and the seller should acknowledge payment received. thats it. thats the whole "security" i want from the internet. Now, if there is someone who wants to impersonate my news website and supply me a falsified news article about harmless kittens, maybe i should be concerned about why i am being a target instead of protecting that i be able to securely read my harmless kittens news article?
- daveoc64 5y agoPeople often don't think about the transition from a "public" page to a "private" page. Take Hacker News for example. If you go to the home page without logging in, you'll see a list of posts. Does this need HTTPS? Using your logic, it wouldn't. But there's a login link in the top right corner of the page. If someone were to MITM the home page, they could make this login link go elsewhere, and harvest data. The same is true of any site which has links to login/signup/payments/contact forms etc. That describes virtually every site these days. It's much easier to have every part of the site on HTTPS, than to have to worry about this. Plus you avoid the possibility of malicious ads, scripts, and malware being injected into the page.
- 2Gkashmiri 5y agoagreed for the most part. does this MITM happen on the local network level or between the ISP and device or upstream level? genuinely interested in figuring this out
- PeterisP 5y agoRandom examples of attacks through a non-https site with kitten articles (assuming an attacker on a shared wifi doing MITM). 1. inject javascript on the kitten site that, in case if you move on to a different tab for five minutes, redirect the page to a spoofed version of the login page of your payment provider or email account usable to recover other credentials, so that if you go back to that tab you might think that your session there just expired and "re-login". 2. inject javascript on the kitten site that replaces any legitimate links to social media platforms with links to spoofed login pages for these platforms. 3. inject javascript on the kitten site that adds an overlay over the kitten videos where clicking on it prompts you to download video_player_plugin_totally_legit.exe in order to watch the kitten videos. 4. inject javascript that replaces any ads (or just adds them) with attacker-controlled ones; possibly for some targeted scams. 5. inject javascript that runs cryptomining in the background. The attacker earns some pennies, but your computer temperature and battery life starts to suck. 6. perhaps they get to inject a javascript sandbox escape - those are rare and not actively exploited at the moment but if your browser isn't up to date for some reason, then sooner or later another exploitable vulnerability will appear again in the wild. In short, any http-only site is effectively potentially fully attacker-controlled for malware delivery, as much as websites can be used for malware delivery.
- trustonfirstuse 5y agoI would like to see browsers support self-signed certificates as first-class citizens. This would probably mean supporting both certificate observatories and trust-on-first-use, at the users discretion.
- xg15 5y agoI think it depends on the actual threat model. It's a bit weird that HTTPS-everywhere was initiated in the aftermath of the Snowden leaks. If your enemy is the CIA or NSA etc, HTTPS probably won't help you: They can compromise your CDN or simply go for your hoster directly. However, there are many smaller and more common threats against HTTPS provides significant defense that wasn't there before. In particular manipulative ISPs or public WiFis or third parties who are logged into the same WiFi as you and are capturing traffic. (Remember Firesheep etc) That being said, I also believe there are some significant downsides to the HTTPS push (and also DoH, eSNI and friends) that browser vendors refuse to address. In particular: - It's a huge driver of "platformisation" of the web: To access an increasing amount of browser features, you now have to rely on third party services - at the very least, you need a domain. This is particularly problematic for hobbyist projects, local-only networks and home servers. - It normalizes a situation where network traffic is treated as a black box. It's a good thing if my ISP or the cafe I'm working in can't inspect my packets - it's highly problematic if my company's admin has no idea what is going on inside the network or if I can't even inspect traffic from my own devices. I'm seriously wondering who is protecting against what here. This seems less for protecting users against snoopers and more for protecting tech companies against their own users - which is really the opposite of privacy.
- marginalia_nu 5y ago> - It normalizes a situation where network traffic is treated as a black box. It's a good thing if my ISP or the cafe I'm working in can't inspect my packets - it's highly problematic if my company's admin has no idea what is going on inside the network or if I can't even inspect traffic from my own devices. I'm seriously wondering who is protecting against what here. This seems less for protecting users against snoopers and more for protecting tech companies against their own users - which is really the opposite of privacy. Yeah, this is... troublesome, especially how fond software developers seem to be of telemetry these days. For software you haven't compiled yourself, that's completely opaque data leaving your network. Especially in the light of how incredibly difficult it is to disable that telemetry collection in Firefox, it's not a great look for mozilla. I don't know if this is the authoritative guide du jour, but the steps usually go something like this: https://gist.github.com/gamunu/7fbee4e2318fdc080395a7f74cc34fe9 https://gist.github.com/gamunu/7fbee4e2318fdc080395a7f74cc34... I'm not sure this trust we're effectively being coerced to put in software and platforms is great from a privacy standpoint. But as you said, there has not been a lot of talk about this.