4 ms·
When the big push to HTTPS came around, I was all in favor of it. Now... I'm more skeptical. Not everything has to be HTTPS. And I've become aware that many
by reaperducer 6y ago
When the big push to HTTPS came around, I was all in favor of it. Now... I'm more skeptical. Not everything has to be HTTPS. And I've become aware that many of the sites I visit are HTTP only and will never become HTTPS because of their age, or the lack of technical ability of their owners. HTTPS also has the side effect of obsoleting older hardware for no real reason. I have devices that work perfectly fine, but can't be upgraded to the latest whiz-bang encryption du jour.
A vintage computer software archive doesn't need to be HTTPS. A local historical society doesn't need to be HTTPS. A color picker doesn't need to be HTTPS.
I still think HTTPS is a good thing, but I also see it as a way of marginalizing and eventually eliminating a very large portion of the content on the web. Much of it is the very content that made the web so popular in the first place.
I think I first became skeptical when Google said it would rank HTTP sites lower. This fits in with Google's general direction of making any content older than 4 years inaccessible, and creating its own information ecosystem in which to corral people. Google can now delist a huge swath of the internet and shrug its shoulders and say, "because security!"
I think a good compromise would be for browsers to make connecting to an HTTP web site a lot less scary. Yes, tell people the connection is old-fashioned, and may be public. But don't block the page and put up big red scary icons and make people enter the system password to view Aunt Harriet's Really Good Muffin Recipe. It just seems like the antithesis of what the web was built for.
- prepend 6y agoI like using http where appropriate and not wasting resources. I publish a blog and there’s no need for https. Adding https just adds a little more effort and provides no benefit to the user. I guess if you count the ISP not knowing, but Google knowing, that you’re visiting my blog, then that’s a reason. But that’s a user issue, not a server issue. Practically, my host does all the cert stuff for me and it’s not hard. I just don’t like the gradual complexification of the web when there’s not a good reason. Moving more stuff to ssl that doesn’t need to be just burns up extra compute. I hope someone calculates the carbon footprint of SSLing all the stuff that doesn’t need SSL. While each action it tiny, there’s trillions of cpu cycles wasted on encrypting stuff that doesn’t benefit from encrypting.
- alecbz 6y agoYou don't care if your blog's content gets MITM'd?
- josefx 6y agoYou mean like by someone throwing up a huge warning that this page is made by the devil himself and unless he recites the right combination of holy words there is nothing you can do to access it? Ran into a few pages that were hijacked that way, some of them at least seemed to go to the expected content when I got rid of the https.
- prepend 6y agoThere’s certainly risk, but I don’t think converting all traffic to ssl is worth it to mitigate the risk. I’ve never run into this situation in many years.
- josefx 6y agoMy comment was actually meant to be sarcastic and a bit over the top. The hijacker in this case would be the browser telling me that the page is not secure and as far as I remember valid certs are enforced to the point where a user can't bypass the error in some cases. In my experience https has always been more of a hurdle when I was looking for some obscure information hidden away on barely maintained websites.
- prepend 6y agoI remember where it used to be fun to do stuff like that, or reverse all the images in pages, etc so thought it was a reference to just general monkeying around with http traffic that won’t work with https. I get maybe 20 hits a year so I would probably think it funny if someone was interested enough to do this.
- prepend 6y agoNo. It’s just static content, there’s no registration and all usage is anonymous. I collect no data. Someone can mitm if they wish, although there’s little motivation. The risk of harm is that someone could try to misrepresent content or something, but again who has motivation and even if they did it would eventually be repaired.
- caymanjim 6y agoAll Chrome does when you visit an http site right now is put a subtle white warning icon and the words "Not Secure" next to the location bar, in lieu of the lock icon you get with https. There are no blocks, no big red scary icons, no password requests. The content on the page renders identically to a secure page. Technology moves on, and encryption is important, even if there are some cases where it's not strictly vital. Sure, some recipe page isn't a big deal, but there are plenty of sites out there that accept personal information and still have to be dragged kicking and screaming into the present to secure that information. Sadly the only thing that's going to solve that problem is forcing https-only at some point in the future.
- reaperducer 6y agoAll Chrome does when you visit an http site right now is put a subtle white warning icon and the words "Not Secure" next to the location bar That's great. But Chrome isn't the only browser in the world. My point about browsers entirely blocking HTTP pages, putting up red scary icons and requiring a system password currently exists in Safari, both desktop and mobile. Technology moves on This is a lazy argument. And in my opinion, meaningless. encryption is important You are correct. But it is not required on every web site any more than everyone needs to carry a gun into a library to look up recipes.
- criddell 6y agoA reason for pushing everything to HTTPS (even local historical societies) is that it protects the rest of us from a weapon like China's Great Cannon. https://en.wikipedia.org/wiki/Great_Cannon https://en.wikipedia.org/wiki/Great_Cannon
- paxys 6y agoNo browser does what you are saying. And I don't get what hardware age has got to do with anything? The moment you use an ISP that injects its own ads into web pages you will realize that HTTPS is absolutely essential everywhere.
- reaperducer 6y agoNo browser does what you are saying Safari has been doing this for at least two years. And I don't get what hardware age has got to do with anything? Not every browser gets upgraded to the latest HTTPS. There are millions of televisions, game consoles, older computers, and other devices that can only browse HTTP, or older versions of HTTPS. They will not be upgraded by their manufacturers. I don't think making those still capable devices less functional is a good idea just because "technology moves on."
- paxys 6y agoI just tried many http websites on Safari and am still not sure what you are talking about. They all work perfectly fine, without any warnings. > Not every browser gets upgraded to the latest HTTPS The solution to that isn't to compromise on security and privacy but rather make these devices upgradable/moddable.
- reaperducer 6y agoI just tried many http websites on Safari and am still not sure what you are talking about. They all work perfectly fine, without any warnings. Then I will thank Apple for changing things and making them less scary already. The fact is that this is exactly how Safari used to handle things. I know because I got many angry screenshots from C-level people in my company when some of our web sites started showing up that way due to a misconfiguration by the IT department. Here is a picture of a similar warning. This is for an SSL error, but the ones Safari used to display for HTTP were nearly identical: https://www.digicert.com/dc/blog/safari-11-introduces-improved-ui-certificate-warnings/ https://www.digicert.com/dc/blog/safari-11-introduces-improv...