3 ms·
There is a reason to read Wikipedia via https: ISP can otherwise inject ads or even change the page. This has actually happened.
by Jaxan 5y ago
There is a reason to read Wikipedia via https: ISP can otherwise inject ads or even change the page. This has actually happened.
- dusted 5y agoThat's not a good reason to take away my choice, and rob me of the opportunity to access this information on an older device if I wanted to.
- smackeyacky 5y agoProxies like WeBone can solve that. https://github.com/atauenis/webone https://github.com/atauenis/webone I use it for a solaris install. https://smackeyacky.blogspot.com/2021/10/hacker-news-in-hotjavatm-for-solaris.html https://smackeyacky.blogspot.com/2021/10/hacker-news-in-hotj...
- yesenadam 5y agoWow, WebOne looks awesome, thank you! My second computer is a 2005 mac mini..and it can't see ~98% of the web. I'll try that.
- dusted 5y agoI appreciate the effort, but there's something that rubs me the wrong way about the state of this "force the world to always encrypt and offer no alternative", the same beef I have with Gemini. "Take perfectly good protocol" -> "Wrap encryption around it" -> "Only offer encrypted version even though the plaintext version is right there" -> "Use third-party tool and extra infrastructure to unwrap perfectly good protocol before it can be used".
- smackeyacky 5y agoI sympathise somewhat but unfortunately the popularity of the internet means those innocent days of unencrypted information have been made dangerous due to too many bad actors. Like usenet, it's gone, it's not coming back. We shrug and move on.
- samatman 5y agoI mentioned this in another thread, but given a secure way to acquire public keys, MITM attacks can be fully mitigated with signatures rather than payload encryption. A tiny client doesn't have to bother checking this signature, anything capable of receiving encrypted data could be just as sure that the payload is byte-identical with the author's intention as TLS makes possible. The difference is everyone gets to read your postcard if they want, but I'm with you: if I have an AVR barely able to GET the weather report, and strip numbers out of it if the JSON schema doesn't change even slightly, what problem is going to arise from some bad actor reading that packet on the way in? If Mallory starts messing with my dumb Arduino garden I can set up a firewall that checks the signatures. It's progressive enhancement with graceful degradation.
- coldtea 5y agoNobody took away your choice. You just need to implement/find SSL for that older device.
- dusted 5y agoI think you've got something mixed up here, it's not that more effort is required by either party, it's just NOT to block port 80, and NOT write explicit redirect rules, and poof, stuff works.
- Someone 5y agoYou may not need that extra protection (now), but society does. It’s just like all the other kinds of safety measures we expect, such as seat belts, regulations w.r.t. food safety, fire protection, standards for tool safety, etc. Nothing of that is needed, until you need it (I’ve never needed seat belts or airbags, for example, but can understand society requiring them) If the industry hadn’t forced the world to https, I think governments would have.