Re:Widespread Hijacking of Search Traffic in the United States
by daemonize on Friday August 05, 2011 @04:15PM
(#2851567)
This says a lot about the ISP's ethics if they are shown to be consenting to this. One thing I didn't see in the EFF article is something a user could do about it: use SSL! This may eventually force these companies into more nefarulious and active techniques of hijacking, but it should alleviate the basic technique they are employing now, if i am not mistaken.
Re:Widespread Hijacking of Search Traffic in the United States
by osivertsson on Friday August 05, 2011 @04:18PM
(#2851580)
From the EFF article:
"And the best protection against the privacy and security risks created by this type of hijacking is to visit sites using HTTPS rather than HTTP, which can easily be achieved using EFF's HTTPS Everywhere Firefox extension"
Re:Widespread Hijacking of Search Traffic in the United States
by Cushman on Saturday August 06, 2011 @12:43AM
(#2853038)
I don't know why you were downvoted for this, it's a very cogent point— most users would probably click through a big red screen that says "DO NOT VISIT THIS WEB SITE!" We need to be thinking of them when we design our security model.
Re:Widespread Hijacking of Search Traffic in the United States
by rwolf on Friday August 05, 2011 @04:51PM
(#2851713)
This is something I keep circling around. The host doesn't seem like a thing you could encrypt, because the intermediaries need to know where to send your packets. It seems like https encrypts the headers: http://stackoverflow.com/questions/187655/are-https-headers-...
but does this include the Location header?
Re:Widespread Hijacking of Search Traffic in the United States
by paxswill on Friday August 05, 2011 @04:58PM
(#2851744)
The HTTP request itself is encrypted, but the IP packet (including the source and destination IP addresses) is not. SSL/TLS is application level encryption, and if you wanted to encrypt the actual packet, you need to switch to something like IPsec, but even then you need some sort of routing method (which I can't remember).
Re:Widespread Hijacking of Search Traffic in the United States
by count on Friday August 05, 2011 @05:23PM
(#2851837)
IPSec can work in many different ways. One of those is to encapsulate the entire packet as the encrypted payload of a new packet, with the new packet having headers in plain text leading to the other end of the IPSec tunnel. That other end will then decrypt and forward as appropriate (this is called a 'tunnel').
Re:Widespread Hijacking of Search Traffic in the United States
by count on Friday August 05, 2011 @05:21PM
(#2851824)
Yes.
SSL / TLS happens below HTTP at the socket layer. This is why you couldn't have vhosts's using SSL on a single IP for a very long time (the webserver wouldn't know which certificate to use).
"And the best protection against the privacy and security risks created by this type of hijacking is to visit sites using HTTPS rather than HTTP, which can easily be achieved using EFF's HTTPS Everywhere Firefox extension"
(And it's worth noting that proxies can unwrap HTTPS).
http://en.wikipedia.org/wiki/Internet_Explorer_6
They cannot get at the plaintext without a certificate warning (or installing a certificate in the user's browser beforehand).
Which will get clicked through anyway, so, uh, the security is kinda moot. =)
If you use Chrome a quick way to add it as a search engine: https://chrome.google.com/webstore/detail/lcncmkcnkcdbbanbja...