3 ms·
> Christ you are ignorant about this kind of stuff. Dude, I'm TRYING to have a discussion here. And frankly, I'm not fully convinced about the arguments that a
by dragontamer 8y ago
> Christ you are ignorant about this kind of stuff.
Dude, I'm TRYING to have a discussion here. And frankly, I'm not fully convinced about the arguments that a lot of people are making here. Lobbing personal attacks is not cool, no matter the subject matter.
-----------
So hypothetically, you're saying a man-in-the-middle attack is going to change the content of my files. I understand.
Now tell me: how does HTTPS secure against that if Comodo certificates (or other poor-security certificate authorities) continue to exist?
A SINGLE bad certificate authority trusted by any of the major vendors would allow the attack you so described happen over HTTPS.
I have seen these things happen. HTTPS is not a magic cure-all, not while globally trusted bad CAs exist. Bad actors can still MITM HTTPS sites with a fake cert.
ISPs typically have some degree of HTTP proxying and caching available btw. You don't benefit from HTTP proxies / caches if you encrypt everything. So there's a reason. And if the bad actors can attack HTTPS with a MITM attack anyway, there's not much to gain from HTTPS from my viewpoint.
- pixl97 8y agoBecause with ssl they still have to attack your site. Without ssl any attack is generic and easy.
- dragontamer 8y agoI'm not convinced of your assertion. If a user goes to http://site.com http://site.com, even if you have a redirector to the https://site.com https://site.com version, the https version can be MITM'd with a self-signed certificate.
- not_kurt_godel 8y ago> If a user goes to http://site.com http://site.com, even if you have a redirector to the https://site.com https://site.com version, the https version can be MITM'd with a self-signed certificate. At which point their browser will give them a big scary security warning.