Live data from Hacker News

ISP Advertisement Injection - CMA Communications

zmhenkel.blogspot.com

41–50 of 81 posts

Re: ISP Advertisement Injection - CMA Communications

#41

This is an interesting problem. On a broadcast channel, when a local station attempts to replace the ads the network has put in their shows, with their own ads, the network has some leverage to shut down that process. But on the Internet there are a bunch of web sites and they don't have any leverage at all. They could do an IP filter, which is to say put up a page "This site unavailable on this ISP's network" when a…

"on the Internet there are a bunch of web sites and they don't have any leverage at all"

They could use TLS...

Re: ISP Advertisement Injection - CMA Communications

#42

HTTPS everywhere would solve this, and the Comcast Javascript injection - I wonder how many more people will deploy things like this before that happens?

You shouldn't have to encrypt your data to stop your ISP from actively 1) scanning and 2) corrupting it. What is the FCC good for?

It is not just about your ISP, it is about all the ISPs between you and the website.

Re: ISP Advertisement Injection - CMA Communications

#43

"knowingly and with intent to defraud, accesses a protected computer without authorization, or exceeds authorized access, and by means of such conduct furthers the intended fraud and obtains anything of value, unless the object of the fraud and the thing obtained consists only of the use of the computer and the value of such use is not more than $5,000 in any 1-year period" Injecting or replacing ads in other people'…

Wouldn't this depend on the TOS of the ISP? Perhaps by signing the contract you "authorise" this. This sort of thing doesn't surprise me any more. AFAIK DNS on every major ISP in the UK is broken, there is no NXDOMAIN. Unresolvable domains are simply redirected to a specific IP address which happens to host a page of ads and a search bar on port 80. This might not matter to most people, but it's a huge PITA when I'm…

FWIW, I haven't noticed this on any of BT, Sky or Virgin.

Re: ISP Advertisement Injection - CMA Communications

#45

"knowingly and with intent to defraud, accesses a protected computer without authorization, or exceeds authorized access, and by means of such conduct furthers the intended fraud and obtains anything of value, unless the object of the fraud and the thing obtained consists only of the use of the computer and the value of such use is not more than $5,000 in any 1-year period" Injecting or replacing ads in other people'…

Wouldn't this depend on the TOS of the ISP? Perhaps by signing the contract you "authorise" this. This sort of thing doesn't surprise me any more. AFAIK DNS on every major ISP in the UK is broken, there is no NXDOMAIN. Unresolvable domains are simply redirected to a specific IP address which happens to host a page of ads and a search bar on port 80. This might not matter to most people, but it's a huge PITA when I'm…

Maybe we should all start packing our own TOS's in request headers... :)

Re: ISP Advertisement Injection - CMA Communications

#46

Earlier quoted context omitted.

We hope ads/no-ads arms race would end there. But I could easily see some unscrupulous/greedy ISPs then resorting to setting up SSL proxies to MITM your ostensibly secure traffic, as some private organizations (schools, corporations) already do.

That's a good way to get yourself the CA death penalty.

So? If Comcast does it, what are they going to do?

Re: ISP Advertisement Injection - CMA Communications

#47
post #28

Earlier quoted context omitted.

https is the wrong solution. that is for preventing others from seeing what you're sending/receiving, not verifying the integrity of what is sent/received. well, it does do that too, but it adds extra unneeded overhead by encrypting everything. Besides, the ISP can easily man-in-the-middle any connection you make and then inject their ads into the webpage, even if you use https. The correct solution is signing the we…

If TLS could negotiate certificates instead of supporting one and only one, the backbone of any sane "virtual host" system, then https: wouldn't be a big deal. It'd be the default. Now you need a separate IP (expensive) or port (annoying) for each virtual host configured with a different SSL cert. This has to stop, but it will not be easy to fix.

RFC 3546, which includes TLS Server Name Indication, has existed since June 2003. The problem preventing deployment is the lack of client support, especially Internet Explorer on Windows XP and Android 2.x [1].

--

1. http://en.wikipedia.org/wiki/Server_Name_Indication#No_suppo...

Re: ISP Advertisement Injection - CMA Communications

#48
post #28

Earlier quoted context omitted.

https is the wrong solution. that is for preventing others from seeing what you're sending/receiving, not verifying the integrity of what is sent/received. well, it does do that too, but it adds extra unneeded overhead by encrypting everything. Besides, the ISP can easily man-in-the-middle any connection you make and then inject their ads into the webpage, even if you use https. The correct solution is signing the we…

If TLS could negotiate certificates instead of supporting one and only one, the backbone of any sane "virtual host" system, then https: wouldn't be a big deal. It'd be the default. Now you need a separate IP (expensive) or port (annoying) for each virtual host configured with a different SSL cert. This has to stop, but it will not be easy to fix.

[deleted]
Post reply on HN