8 ms·
RIP HTTP
- themodelplumber 4y ago> But be careful, it could have had ads or malware injected and likely was spied on, by ISPs, governments, hotspots, and other malicious actors. And it also suffers a ranking punishment. Whoa whoa whoa! That is a lot to unpack right after that pledge. "I know I suck but I pledge to be here for you always!" This feels like some kind of a personality crisis. Maybe we should take a moment to feel out the pros and cons more gently. Surely _captive portals_ can't be the only thing going for you, HTTP ol' buddy! (I mean...surely?)
- askvictor 4y agoI use sites like this a fair bit while developing embedded network code.
- teh_klev 4y agoNot that I make a habit of correcting other's spelling and grammar, however: ocassionally -> occasionally
- superkuh 4y agoThe real death of HTTP isn't that HTTPS is being forced. That's good and bad but at least you can chose and it's HTTP underneath. The death of HTTP is "HTTP"/3 which is barely related to past HTTP protocols and doesn't even allow a choice. Eventually the megacorp browsers will drop real HTTP/1.1 support from their browsers for QUIC based transport. That will be the death of HTTP.
- kortex 4y agoWhat do you mean by "doesn't even allow a choice?" Like there's no option for non-secure? Also I would not be too hasty to expect the death of any widely used protocol. You can still access gopher sites.
- Spivak 4y agoCorrect, TLS is built into the protocol itself instead of it being HTTP wrapped in a TLS stream.
- beardog 4y ago> What do you mean by "doesn't even allow a choice?" Like there's no option for non-secure? Yep. http/2 in browsers does not support plaintext, the same will likely be true for QUIC >You can still access gopher sites. Not via vanilla mainstream browsers.
- Gigachad 4y agoPresumably the non secure equivalent for internal services will just be a self signed cert. So you don't lose any existing capabilities.
- bawolff 4y ago> Yep. http/2 in browsers does not support plaintext, the same will likely be true for QUIC This is mostly because internet middle boxes choke on plaintext http/2. Plaintext http/2 does not work for a not insignificant portion of users so browsers didn't bother to implement. But its a thing that does exist and you can use if you really want. Just not on the public WWWW.
- perydell 4y agoSee neverssl.com. It has been around for a long time and is useful for making sure you see Wifi terms pages.
- yftsui 4y agocaptive.apple.com does the same trick with a smaller payload.
- benatkin 4y agoWhere can I go that has a bigger payload? When I've successfully opened a site on an unfamiliar WiFi network I'd like to know up front if I'm gonna have trouble loading stuff.
- graiz 4y agoNeverSSL is the way to go - they have a number of cache-busting tricks that I haven't seen on other sites.
- password4321 4y agoNot anymore? (This discussion is pretty much a dupe.) https://news.ycombinator.com/item?id=35789730 https://news.ycombinator.com/item?id=35789730
- lolinder 4y ago
- p-e-w 4y agoGood riddance! That the web's core transport protocol used to lack encryption and authentication is an artifact from a time when nobody thought that the Internet was ever going to be used for anything of real-world value. HTTP is a dinosaur. The age of the dinosaurs is over. It's slightly cool and quirky that it used to be a thing, but we should all be glad that it isn't anymore.
- pabs3 4y agoHmm, this website supports https with an expired self-signed cert, but the https request never completes and repeats over and over again.
- mekoka 4y agoWe apparently still need http to detect wifi portals.
- jaimex2 4y agoThere's been countless RFCs for a DHCP hook. ie https://www.rfc-editor.org/rfc/rfc8910 https://www.rfc-editor.org/rfc/rfc8910
- pedropaulovc 4y agoMy go-to HTTP-only endpoint is http://example.com http://example.com. It should be usable for as long as IANA and the Internet as we know it exists.
- ThrowawayTestr 4y agoWeird, I can only access it on mobile data but not on my wifi.
- judge2020 4y agohttp://captive.apple.com http://captive.apple.com
- Klonoar 4y agoInterestingly enough this doesn't work for me on certain public wifi networks. I often have to go to a different HTTP-only URL, it's weird.
- rjh29 4y agoI've also had situations where _only_ neverssl.com wouldn't load but other http sites would switch to https with an invalid cert error. It's really weird.
- guidoism 4y agoOh cool. I worked on the networking layer of the first Kindle iOS (née iPhoneOS) app and that captive portal stuff was a pain in the ass. I would just walk across the street to Tully’s and use their wifi to get that pop up.
- smsm42 4y agoI use neverssl.com
- pabs3 4y agoThat supports https too, so current/future browsers will auto-upgrade to https.
- ThrowawayTestr 4y agoHTTP belonged to a simpler time, the same way in some communities you don't lock the front door.
- appleaday1 4y agothe same time I could run email servers on the internet and not have to worry about people breaking into it :/
- notfed 4y agoSeems a little dramatic... HTTP isn't going anywhere. HTTPS is literally just HTTP with a TLS layer on top.
- Gigachad 4y agoHTTP/3 does not include capability for non-encrypted connections.
- Matthias247 4y agoVery true. Actually HTTP now also just refers to the semantics. HTTP/2 and HTTP/3 are still HTTP. They all support requests, responses, verbs, status codes, headers, caching semantics, etc. The only thing that might become less common is "HTTP/1.1 over TCP". But I get that this is much more verbose to write than "RIP HTTP".
- kazinator 4y agoThere are some small embedded devices that only speak HTTP. E.g. I have a power outlet with a web interface. You can power cycle outlets through that. It speaks only HTTPS. (The current revision of the product has a better embedded system in it with a better TCP/IP stack, and supports https.)
- jaimex2 4y agoPretty ignorant. HTTP is alive and well. Most people don't realise a lot of software/OS updates come through HTTP so that HTTP caching servers have an opportunity to do their thing. But but... what abouts th3 securaitai? The updates are signed. Tamper with them all you like.
- chrismorgan 4y agoHTTPS is not just about tamper protection, but also about confidentiality. Do you want an attacker to be able to identify exactly which packages and which versions of packages you have installed? (Mind you, you’ll often be able to do a good job of guessing based on the side-channel leak of how much data is transferred.) See also: pervasive monitoring is an attack <https://www.rfc-editor.org/rfc/rfc7258.html https://www.rfc-editor.org/rfc/rfc7258.html>. I would expect all major operating systems to deliver their updates over HTTPS these days. (I know Arch Linux’s mirrors are widely available over HTTP and HTTPS, but the first mirror in the list is HTTPS, so the considerable majority of users will get packages over HTTPS—though since the second is HTTP, all it takes is DNS-blocking geo.mirror.pkgbuild.com to cause it to fetch over HTTP.) As for “so that HTTP caching servers have an opportunity to do their thing”: how much do public intermediaries do caching any more? I don’t know how popular that kind of thing ever was, though I know it did happen sometimes, but with how uncommon plain-text HTTP is now, I’d honestly expect most vendors to just drop that functionality as almost-unused complexity.
- bawolff 4y agoYou mean like - https://justi.cz/security/2019/01/22/apt-rce.html https://justi.cz/security/2019/01/22/apt-rce.html? tbf, I'm being a bit hyperbolic. Its totally reasonable to have security at different layers. One good thing about HTTPS though is it is a very well tested layer. Crypto is such an easy thing to screw up, even when doing just basic stuff.
- no_carrier 4y agoCaptive portals can and should have TLS enabled, even if they're internally served, there's nothing stopping you putting on a cert signed by a well known CA. The way I handle it is I have the captive portal DNS name in public DNS returning a private address. When I order the CA cert from my cert provisioner of choice, I'm able to pass all verification checks. I'd use LetsEncrypt if I could, but good luck getting that going on a Cisco Wireless LAN Controller.
- Animux 4y agoI would love to know, how your captive portal is getting a valid certificate for https://google.com https://google.com. The problem is: If the first connection of the client is a https connection, your captive portal has no possibility to redirect this request to the portal.
- pixl97 4y agoMy android phone seems to handle this well, not sure how it's detecting this and doing it, but seems like something that needs set on the OS side to detect when this occurs.
- deleted 4y ago[deleted]
- techaqua 4y agomy isp used to inject ads to http sites
- pixl97 4y agoPeople that write articles like that never had that jerk friend that would connect to their LAN and arp flood to take over an IP or setup a pineapple to capture wifi then run a proxy to turn all their images upside down. The way we run public certificates may have 100 holes in it, but the entire thing isn't open for easy attack for anyone that's clever enough to see and modify a packet to whatever they want.
- forgotmypw17 4y agoI'm still using HTTP and plan to continue for the next 25 years or so.[1] It is a highly accessible, highly compatible protocol, highly usable protocol. I also think the MITM risk is overrated compared to how much barrier HTTPS creates to accessing basic information. [1] https://en.wikipedia.org/wiki/Lindy_effect https://en.wikipedia.org/wiki/Lindy_effect
- GenericDev 4y agoThey hate you because you spoke the truth. So much of security is performance or ruining the convenience of things just for the sake of protecting things. It's really frustrating. But hey it's to protect the kids or something /s
- zamnos 4y agoISPs and coffee shop wifi injecting ads into webpages wasn't a theoretical attack, but I'm more curious: Which barriers with HTTPS are you referring to?
- josefx 4y agoWith how most of the internet already looks like without adblocker the difference would probably be impossible to even notice. Edit: Also around half the pages I currently have open are passing through cloudflare anyway and signed by them, so a third party hijacking the connection to throw in ads is just one business minded CEO away.
- zamnos 4y agoI mean, it's not impossible for Matthew Prince, or his successor, or more likely his successor's successor, will just throw away the company by injecting unauthorized ads, but until they actually do, let's not pretend they have? Cloudflare's customers aren't going to stand for that and will find a new CDN if it was ever shown to be the case that Cloudflare was intentionally altering content they're rehosting. Cloudflare's imperfect, but Prince isn't that dumb, so we're years away from even the hint of that being possible.
- 4y ago
- JonathanBeuys 4y agoHTTPS is still a pain in the ass. If letsencrypt would offer wildcard certificates with their url based authentification as they offer for non-wildcard certificates, it would be annoying but bearable. But having to tinker with the DNS infrastructure for each project which wants to use domain wide HTTPS is so much hassle.
- JodieBenitez 4y agoI've been using Caddy for personal projects and I don't even think about HTTPS anymore. Except when I have to use another web server at work :-/
- JonathanBeuys 4y agoThat is fine for simple projects where all you have to do is automate cert updates for the root domain or a few subdomains. The problem is not to automate this process. It's easy to write a shellscript that regularly updates certs for a root domain or some subdomains. The problem is that letsencrypt does not offer url based authentification for wildcard certs. So you have to temper with your DNS infrastructure so that you can automate DNS updates for your domain.
- bawolff 4y ago> The problem is that letsencrypt does not offer url based authentification for wildcard certs. For good reason though. You shouldn't be able to get a cert for a domain you cannot prove you control. Lots of people have webserver access to a specific domain but not all subdomains.
- JonathanBeuys 4y agoWhich users have access to put files into .well-known/ of the root domain? I am not aware of any service that allows that. Can you give an example? What do you mean by "lots of people"?
- ozim 4y ago
- ghoshbishakh 4y agoEvery "web" page is using HTTP. With or without TLS.
- nrabulinski 4y agoI always just open the router IP and the captive page shows up I never even thought of opening a http website
- brokenmachine 4y agoHow do you know the router IP when you're on a phone? I know you can dive into network settings, but seems like a hassle.
- grishka 4y agoI usually use example.com for this purpose.
- deleted 4y ago[deleted]
- z3t4 4y agoHTTP encryption is a bit overrated. Governments only care about which sites you read and httpS don't help against that. TSL is also designed to be man-in-the-middle'd. Check your root certificates and ask yourself if you trust all those organizations. You will also likely find your ISP has a root certificate. The TLS handshake takes a lot of computer resources and makes your web experience slower. Encryption is good when you login to your bank over a random public wifi. It's unnecessary for public and open web sites that don't require username/password to login.
- pas 4y agowhat's the status of DoH deployment and ESNI?
- criddell 4y agoHTTPS also protects us against attack tools like China’s Great Cannon. https://citizenlab.ca/2015/04/chinas-great-cannon/ https://citizenlab.ca/2015/04/chinas-great-cannon/
- spacebanana7 4y agoHTTPS still provides some protection against MITM attacks. Also restricts the ability of ISPs to inject ads into other people's sites.
- kryptiskt 4y agoHTTPS by default came just in time for protecting us from ubiquitous injected ads from ISPs and wifi APs, we are lucky to not have experienced the worst of that.