3 ms·
Because there are still plenty of valid use cases for HTTP.
by bityard 7y ago
Because there are still plenty of valid use cases for HTTP.
- jaas 7y agoNo there aren't. All HTTP traffic can be modified, which means it can deliver any malicious payload to the server or client. It's dangerous not to use HTTPS, period.
- zozbot234 7y agoThis is silly, as the endpoint you're connecting to could also be malicious. If you're worried about trusting your intermediary, you can just VPN to a trusted host and use it as a proxy.
- neop1x 7y agoOr you can SSH to the server and read it from http://localhost http://localhost (if you have access). But there can still be malicious software running, intercepting syscalls or your localhost domain can point to a malicious IP. :/ Software can't be trusted. Period.
- tripzilch 7y agohttps://news.ycombinator.com/item?id=22997403 https://news.ycombinator.com/item?id=22997403 this comment mentions their provider inserts ads in non-https traffic.
- deleted 7y ago[deleted]