2 ms·
No 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
by paxys 6y ago
No 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...
- paxys 6y agoThere has never been anything like this in Safari for plain HTTP. Your company was probably just dealing with bad certificates.
- remram 6y agoThe point I think is that HTTP never changes, while HTTPS constantly evolves and deprecates hash functions, ciphers, and authorities. If your router's or printer's web management interface was written more than a couple of years ago, it is probable that it will show up as insecure or even have a big warning screen.